Dynamics Business Central / NAV Development Developer Digest - Vol. 408
ArcherPoint’s Developer Digest focuses on Microsoft Dynamics 365 Business Central and Dynamics NAV development. In Developer Digest Volume 408, you’ll see how to access telemetry data from AL and integrate into Business Central, migrate a NAV database to the cloud in one step, and the 21.1 Business Central cumulative updates have been released.
The Dynamics NAV and Business Central community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of sharing helpful information with one another to help customers be more successful.
As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media…for everyone’s benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share the wealth of information with everyone who might not have the time to check out the multitude of resources out there?
Thus, the ArcherPoint Microsoft Dynamics NAV/BC Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV/BC experts and devotees around the world. We hope these insights will benefit you, too.
Accessing Telemetry Data from AL Code and Developer Tip
Erik Hougaard shows how to access telemetry data from AL code and feed it into Business Central. Hougaard walks you through what telemetry data is needed with this example, such as registration keys data and error messages, and how to integrate this AL data into Business Central by using web services.
Developer Tip from the comments:
Dmitry Katson comments on the last “rows” array code and shows that the values are JSON Values. He points out that “to get appInsights values we need to know the exact order of columns and then associate values to columns” and demonstrates below:
var columnJV: JsonValue; valueTxt: text;
row.Get(0, T); //eventId columnJV := T.AsValue(); valueTxt := columnJV.AsText()
row.Get(1, T); //companyName columnJV := T.AsValue(); valueTxt := columnJV.AsText()
row.Get(2, T); //message columnJV := T.AsValue(); valueTxt := columnJV.AsText()
Microsoft Dynamics 365 Business Central Online Cumulative Update for November
- Access Business Central with your Microsoft 365 license
- Embed Business Central in Teams tabs
- Auto-Save as you work: due to popular demand, administrators can now choose to turn on or off the new auto-saving behavior using Feature Management
- Business Central is available in 11 more countries
- Accessibility declaration for Italy available
- Use SharePoint Connector module in System Application to build integration between Business Central and SharePoint
- Use multiline text fields with Word mail merge
- Sync users based on environments security group
Zhu also discusses the Microsoft announcement about Microsoft Teams users being able to access Business Central data, regardless of whether they have a Business Central license or not.
How to Migrate an Older Dynamics NAV Database to Business Central Cloud in One Step
Sounds too good to be true but Marije Brummel, a Microsoft MVP and BC Developer, demonstrates how to migrate an older Dynamics NAV database into BC Cloud. She says that the salient detail is understanding that the whole migration is done at T-SQL level and it’s one big Transact SQL Script.
Brummel: “We all know that the NAV schema has not been changed that much since 1985. A customer is still a customer, and an item is still an item. What if we ‘fool’ the integration runtime into thinking that it is looking at a Spring 2019 database instead of a NAV 2017 database?
Below are some first steps found on her blog post:
ALTER DATABASE [NAV2017] SET COMPATIBILITY_LEVEL = 130
ALTER DATABASE [NAV2017] SET CHANGE_TRACKING = ON (CHANGE_RETENTION = 10 MINUTES)
CREATE TABLE [dbo].[$ndo$tenantdatabaseproperty](
[versionno] [int] NULL,
[collation] nvarchar NULL,
[applicationversion] nvarchar NOT NULL,
[percompanyschema] [tinyint] NOT NULL
) ON [PRIMARY]
Brummel cites that you can’t go into production with this, but it will save dozens or even hundreds of hours preparing database on-premise first.
Read the full blog post, “Migrate an Older NAV Database to BC Cloud in Only One Step.”
Interested in Dynamics NAV and/or Business Central development? Be sure to see our collection of NAV/BC Development Blogs.
Read “How To” blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.