Dynamics NAV / Business Central Developer Digest - Vol 380
ArcherPoint’s Developer Digest focuses on Microsoft Dynamics 365 Business Central development and Dynamics NAV development. In Developer Digest Volume 380, we discuss the purpose of SetCurrentKey today, Microsoft office hours, and more.
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…so everyone can 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 this great information with everyone who might not have the time to check out the multitude of resources out there?
So, 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.
The Purpose of SetCurrentKey
Kyle asks: “Is there any point to using SetCurrentKey these days, or is the service tier smart enough to just let SQL figure out the best key like the SQL gods intended? I am talking about performance, not sorting order.”
Matt T responds: “I am pretty sure it will override it if it thinks it has a better index. It feels wrong to say there’s no point to it, but I’m struggling to come up with a performance reason to do it anymore. AzureSQL will actually automatically create the indexes it thinks you need.”
Jon L adds: “I read somewhere over a year ago that it’s not necessary. SQL handles it, at least in BC. But it definitely still matters to have a proper supporting key on a flowfield. SQL stinks at prioritizing a key for a flowfield.”
Matt T comes back: “In thinking about this more it is probably still a good idea to use SetCurrentKey.
- It’s just better for code readability. I like being more explicit in what you’re telling the system to do and the expectations being obvious.
- The key that you suggest is still heavily weighted in what SQL decided to use. So while it may choose to use something else, it will have an even bigger / more important reason that it chooses to ignore you.
- Azure SQL still has a way to go in terms of the indexes it creates automatically. I was talking with Marije about this and it makes sense. After all, when was the last time you saw a product that did a perfect job, or near-perfect job for that matter, of improving performance without user intervention?”
Microsoft Office Hours with the MS Engineering Team
You might want to bookmark this page and revisit it often as Microsoft updates with upcoming dates and time for Business Central Office Hours Calls. You can also register to view the recordings of previous calls. Topics include:
- Business Central apps in AppSource
- How to use OAuth when calling Business Central APIs
- Cloud Migration
- Using Telemetry to improve partner practices and processes
- Universal Code initiative
- Data Synchronization and Dataverse improvements
Yodlee Bank Feed Integration for Business Central
Noted D365 expert Heinrich Vermeulen shares: “Just some quick feedback following a case this morning on Yodlee bank feed integration. It’s actually pretty simple to test and implement. There is a Microsoft Learn page on this. But the nice thing is Yodlee provides a Dummy Account Generator site where you can create custom test credentials and create or upload test accounts and then link to them using your BC test environment (I used CDX). It really helps to see the mechanics at work before getting a live bank account going.
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.