Welcome back to The NAVCave. I subscribe to way too many blogs and NAV forums. Each of these contributes to a wave of NAV email all the time. I’m going to try and report on some of the interesting bits I find in my inbox.
Two additional AL types have been added, List and Dictionary. While they only work with simple types it’ll be useful to use results in a list.
Along with the List and Dictionary types ForEach has been added to allow iterating over expressions in AL. You can use ForEach over expressions of type List, XmlNodeList, XmlAttributeCollection and JsonArray.
The new translation process decouples translation from development. you can now specify default translation, future updates will provide standard format translation. When the translation file is completed and packaged with an extension it becomes a multilanguage extension! The new syntax is in the article.
On Totovic’s blog he posted a nice summary of the state of NAV and a little pep talk that I’ll summarize.
Dynamics NAV 2017 is the on prem and on cloud ready solution while Dynamics 365 Financial and Operations Business Edition are the SaaS solutions based on NAV. Marko Perisic announced in Madrid and again in Nashville that Dynamics NAV 2018 will launch December 1st 2018. The coolest bit about the new NAV solution is that Visual Studio Code can be used for Extensions v2, this allows folks to jump on the new paradigm before it launches in the spring.
In the spring of 2018 Dynamics 365 Tenerife will release as a cloud SaaS solution as far as on prem goes we’ll see NAV 2018 R2 which we’ll have the same code base as Dynamics 365 Tenerife.. at this point it’s a branding thing or something. but the system will have modern web interfaces and many new features!
One more release in the spring will be Dynamics 365 for Sales App with less features and Dynamics 365 for marketing will be previewed. Both were presented during directions conferences (partner conferences).
The main point he has is that we need to stop implementing an ERP and\or a CRM and instead implement a complete business solution. the end user doesn’t care what it’s called they just want a complete package and Dynamics 365 will cover most if not all the bases. So, instead of selling an ERP we’ll sell a solution where after looking at business needs the right apps and such will be implemented. Now apps will be able to be combined from business edition and enterprise edition to provide more agile implementations. CDS can be used for integrations and on top of Dynamics 365 Apps, powerApps, Flow Office 365, Power BI and 3rd party apps can all be added to the same business environment to provide that complete solution.
Another main point he has is to keep on keepin on, names will change and the process will change but the product will be better for it.
https://totovic.com/2017/10/10/the-future-of-nav-a-small-wrap-up/ On Roberto Stefanetti’s blog he runs through the Certificate of Supply feature of NAV. I’m not familiar with this feature yet so we’ll see what I can learn. Basically when you sell good to a customer in another EU country/region you send a certificate of supply that they sign and return to you. These are sent for sales shipments, service shipments of items and return shipments to vendors.
When the certificate status field is updated a cert is created, once signed and returned the status can be set to received. Changing the cert status auto updates the reciept Date field to the current work date.
Many modify the Receipt date to the date the receive the signed cert of supply, using document linking within NAV you can add a link to the signed cert of supply as well. As always MSDN has the master plans for the process of creating and managing standard certificates of supply.
The associated table, page and report objects in NAV are ID 780.
One can navigate to this section of NAV easiest by searching for cert in the top right of the RTC.
Certificate of supply is enabled on VAT posting setup list page (there’s a checkbox at the VAT setup card page level).
The 3 types of certificates again are, Sales Shipment, Service Shipment and Return Shipment.
Users can retroactively create certificates of supply for documents already created using the create cert of supply if not already created checkbox on the cert of supply edit. (update and work with one of the aforementioned three document types at a time)
The status changes we discussed earlier can be made from the Certificate of supply list page and certs can be accessed from Posted Sales Shipments ribbon
Using the patterns for these docs you can certificate anything or implement similar programs in your business. Anything that would require sending a doc to the customer and receiving it signed.