Cronus | lightweight framework for building event driven systems | Microservice library

Add \ before $

The OData endpoint is different to the API endpoint.

I'd recommend using the API as it's the more up to date and efficient way to interact with data within Business Central.

The documentation for the API endpoint can be found here https://docs.microsoft.com/en-us/dynamics-nav/api-reference/v1.0/, along with some examples such as updating customers, items, etc.

You can use OData to modify data, but only if the underlying object that drives the endpoint is a page (as opposed to a query), and must be marked with InsertAllowed. This is less optimised than the API endpoint. https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/use-odata-to-modify-data

I think a lot of what you did, specifically around data wrangling, was not necessary, especially since you called d3.hierarchy() and d3.cluster() afterwards. I've replaced this with d3.stratify (which deals with hierarchical data that is not yet in the right format).

I've also replaced d3.cluster with d3.tree() because it was unclear to me why you'd want to use d3.cluster here. Your data has multiple parents, multiple roots and even floating nodes, and d3 is not meant to deal with that. My workaround has been to attach pseudonodes to every level, so as to make sure that there is only one node and that all nodes are at the right level at all times. To make sure the links were drawn correctly, I've written a custom getLinks function, that can deal with multiple parents.

I've also written a custom link generator that draws the links somewhat in the way that you want them. d3 doesn't offer much of flexibility here, but you can use the source code for inspiration.

Edit

I've changed the logic to be more focused on which "partners" got a child, so both links to the same child are on the same level - like in your picture. I've also drawn the nodes based on how many partners they have, and have given every link an offset so the lines are more distinct.

I've sorted the nodes so that the real pro-creators are at the top (Zeus), which gives a more balanced and less crowded view.

I finally got the issue. I replaced the httpheader with curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/json')); and that fixed the issue.

If you always invoke coolmailer.pl with a unique argument then you can simply grep it from your list of cronjobs:

The issue here is a null value in C# is not the same thing as a NULL value in SQL Server. One option here might be to use the null coalescing operator ?? when adding the parameters, e.g.

Seems to be due to the fact that you never close your initial while loop: while i < 1. Since the value of i stays at 0, your outermost while loop will never close, causing your program to be stuck in an infinite loop. If you close that loop by setting i = 1 at the end, this particular problem should be resolved.

If you check the input XML carefully there are multiple namespaces (attributes starting with xmlns) associated with the elements in the XML. Since these namespaces are not mapped in the XSLT, the output XML does not show any data.

For the output XML, the elements from which data is being accessed belong to following namespaces

Put the UNION in a view definition and then query the VIEW.