JavaScript

(Update, 20.4.2015: As it turns out – this post is not entirely accurate, as pointed out by Johannes Sebastian. Please read the next post to learn more about which parts are, and which aren’t correct.) Control Add-ins written in C# are not cross-version compatible.

Switching from C# to JavaScript to develop your control add-ins might get you scratching your head more often that your scalp, or nails for that matter, might be happy with. One of those is overloading. In C#, this is a no-brainer: However, when you want to do that in JavaScript, if you are not a…

I stand corrected. A month ago I wrote about how to pass JSON from JavaScript to C/AL and then handle it inside, and what I wrote is not wrong, but I just figured a simpler way. Too bad all this is not documented, but hey – that’s why blogging is fun.

Yesterday, I said I was closing this year of blogging, but I wasn’t really. Closing a year with 39 posts, and leaving a question lingering, wouldn’t be too fair, would it? If you read my last postabout how to pass objects from C/AL to JavaScript , you must have wondered if it’s possible to also pass objects from JavaScript back to C/AL.

Many cool things often go undocumented. I’ve just stumbled upon one of those, and it comes in handy to close this year of blogging. Imagine this situation: you have a server-side .NET object, that you want to pass on to the client.

First of all, thank you all who attended my session today. It was a lot of people in the room, and with the competition from Microsoft talking about a very hot topic in the other, bigger room, I really wouldn’t expect to see all of you there.

Thanks to everybody who attended my session at Directions US in San Diego today. It was a pleasure to deliver it, and I hope you enjoyed it as much as I did. It surely would have been much better if I were not running some kind of a flu, but I won’t complain.

Yesterday evening I spoke at Dutch Dynamics Community event , on invitation by my dear friend Luc van Vugt , and the topic was control add-ins for NAV 2013 R2. Of course, this automatically meant that the audience should see more JavaScript code than C# or C/AL, and that it should be something both fancy and useful.