Dynamics Business Central / NAV Development Developer Digest - Vol. 402

Dynamics Business Central / NAV Development Developer Digest - Vol. 402

ArcherPoint’s Developer Digest focuses on Microsoft Dynamics 365 Business Central and Dynamics NAV development. In Developer Digest Volume 402, you’ll read about what was covered at BC Tech Days, including Business Central and Dataverse, Advanced Topics in Test Automation, Permissions Revisited, BC Performance Toolkit and much more. ArcherPoint’s MVP, Saurav Dhyani, also provides a summary on the recent September BC cumulative updates and a discussion of on premises Designer Extension IDs.

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.

BC Tech Days in the Books

BC Tech Days happened last week with many great topics covered:

  • Business Central and Dataverse
  • Improve Code Quality Using Tools from Microsoft and the Community
  • Empower Citizen and Pro Developers with Power Platform
  • Advanced Topics in Test Automation
  • Being More Efficient with VS Code
  • BC Performance Toolkit
  • Permissions Revisited
  • OAuth Revealed
  • Coding 4 Performance
  • Customizing the Developer Experience
  • Building Collaborative Apps for Business Central with Microsoft 365 and Teams
  • Above & Beyond – When BC is Not Enough
  • Universal Code – Target Must Be Cloud
  • Optimizing SQL Queries in Business Central
  • What’s New in BC Clients for AL Developers

What a lineup! If you missed it, check out the posts on Twitter to catch up on BC Tech Days.

Business Central Cumulative Updates for September 2022

Saurav gives a summary of the BC cumulative updates from September. Read his post for information on the updates for BC 14, 18, 19, and 20. Includes links to details from Microsoft and downloads.

On Premises Designer Extension IDs

Hasse is running into a problem: “Had a(nother) discussion last week regarding how to handle conflicting page extensions from client created designer apps, and I had an idea that I am wondering if anyone has ever tried so they can shoot it down.

Since page extensions are not limited to the licensed object id’s has anyone tried what happens if the license was assigned 51000…whatever instead of starting at 50000. Would the Designer start at 51000 or would it still start at 50000?

Tom makes a guess: “I don’t know what it would do, although I suspect that it ignores the license and looks to the idRanges setting in the app.json file to determine what it should use for object IDs.”

Hasse clarifies his question: “I mean the GUI designer that generates its own extension app. It wouldn’t have an ID range and we haven’t found a setting anywhere, so either it looks at the license, or MS hardcoded it to start at 50000. If it is the latter, we could start assigning the clients custom ranges to 50100 or higher, and we can avoid the conflicting ID.”

Tom rants: “I’m very strongly of the opinion that if anyone is using the GUI designer to create their own extension app, we should strongly encourage them to route changes through us, because we can’t predict what objects will be used and it’s a huge mess on our side.

I’m also very strongly of the opinion that Microsoft needs to get their act together and fix the designer so that it puts its changes in its own object range that isn’t conflicting with our changes, and if I get the opportunity to deliver that opinion to the relevant people at MS who could get it changed, I would do so, probably at a very high volume.

But in the meantime, we need to urge customers to not using that feature. It’s only meant to be used if they’re using a stock BC solution + add-ons; once we start making changes in an app, they must stop using the designer.”

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.

Trending Posts

Stay Informed

Choose Your Preferences
First Name
Last Name
Subscription Options
Your Privacy is Guaranteed