… almost a year of New Development Environment! … and is still in preview !
About Vs Code & Microsoft Al
I had already talked about VS Code, AL and the new development environment before, I had also created a short presentation on slideshare. Since it has been viewed and downloaded by several people, i thought I would integrate it with one related to differences between the two development environments (some of my followers have asked about this topic).
Documentation and books
Currently there is still little available documentation that will probably be integrated shortly, no book has yet been published on the subject, I know something is already in production.
Since Microsoft Doc will now be used as a repository of all Dynamics documentation, I hope it will arrive shortly .. however, that the new development environment is still in Preview!
Below you can find a brief and simple presentation of the differences between the old and the new development environment.
My last presentation on Slideshare “C/SIDE-C/AL Vs VS Code-AL”
Stay tuned for updated documentation and new books!
Dynamics NAV on Docs.microsoft.com LIVE
The Dynamics NAV 2017 developer and IT-pro content is now live at Docs.microsoft.com/en-us/dynamics-nav.
The Docs.microsoft.com site is the home for docs for all Microsoft products and services, and it is replacing the MSDN Library that the Dynamics NAV docs have published to for many years. You can read about why we are leaving the MSDN Library in Jeff Sandquist’s blog post.
Some cool things about the site:
NAV 2018 will be on Docs
Dynamics NAV 2018 docs will publish to the same location, and you’ll be able to switch between versions. More to come on that subject.
Downgrade Production Order Status
Sometimes it is required to perform a status change of a production order that was advanced by mistake .. maybe the error is related to many orders …. With NAV (standard) it is not possible to do
ERROR: “FIRM PLANNED IS NOT A VALID SELECTION”
DOWNGRADE TEST RELEASED TO FIRM PLANNED
However, in order to do this without disturbing SQL Scripts, you can change the state by working only on some tables.
The order should not have been advanced.
I do not recommend reopening a finished order (obviously there are good reasons for various cost problems, traceability, output and consumption, work account etc.)
… If an order is made by mistake, you can reopen it. For example, re-open an released order and return it to a confirmed state.
Below you will find a report that allows you to change the status of a production order (in this case from a RELEASED to CONFIRMED)
REPORT REQUEST PAGE
VARIABLESTABLES TO CHANGE
Have a nice ORDER STATUS CHANGING !
Downgrade Odp to Firm Plannerd Orders.zip
NAV Development Preview – November Update
#VSCODE #dyndev365 #NDPW
and….. “Running C/SIDE and AL side-by-side”
“We’ve implemented support for development using both C/SIDE and AL, as well as the in-client designer side-by-side. When new objects are added or changed in C/SIDE these changes must be reflected in the symbol download in Visual Studio Code using the AL Language extension.
To enable this, new commands and arguments have been added to finsql.exe. For more information about running C/SIDE and AL side-by-side see the documentation.”
POST SOURCE https://blogs.msdn.microsoft.com/nav/2017/11/08/nav-development-preview-november-update/