When you have a couple of job queue entries in your productive system, it can be helpful to have a quick look at the windows eventlog entries, which are connected to the NAV services.
This blog post is primarily directed towards partners who wants to do AL code customization in Microsoft Dynamics 365 2019 release wave 2. Even though the tools can be used for extension development as well, typically people working on extensions already have organized their files.
A week ago, Microsoft came with this message on twitter:
Hot off the press – updated release plan for #MSDyn365BC #2019releasewave2! Catch changes here:
Which basically pointed to an URL that was (for me) difficult to find on Microsoft Docs. I literally had to find the tweet again to find the list of expected features again .. so I figured: If I have a problem finding it, others might have problems as well. So, here it is:
We’ve been doing a lot of Dynamics 365 for Sales and Customer Engagement work for clients who are already using Dynamics NAV and Dynamics Business Central lately. Each of these applications provides some form of CRM functionality, but there is a lot of confusion about when the different solutions might make the most sense. Let’s try to tackle this at a high level…
When you’re developing in C/AL in Business Central/NAV 2018, you might run into this issue: You want to edit the code in an object through the Developer Environment, and the Application automatically crashes or closes without displaying an error message. This occurs when you open a Codeunit or click on C/AL editor in a Page/Table, and it occurs only when you are designing the object and go to C/AL code by hitting F9.
In our Org we have quite a few places were data is auto populated based on other data selected. This however comes with allot of rules. When I started, we had allot of issues where sometimes the incorrect data is selected. This required a rewrite of the filtering to find the correct data but often caused the “fix” to break another set of data combinations.