Dynamics NAV / Business Central Developer Digest - Vol 364
The ArcherPoint Developer Digest blog focuses each week on Microsoft Dynamics 365 Business Central development and Dynamics NAV development. In Developer Digest Volume 364, we discuss the release of Business Central 2021 Wave 2, OneDrive storage integration, problems with publishing an app, 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.
Dynamics 365 Business Central 2021 Wave 2 Released
As of October 1, Business Central 19, 2021 Wave 2 has been released. You can check out What’s New in Business Central blog and attend the Business Central Launch Event on demand to catch up. You can also review the release plan on to see what’s new in 2021 release wave 2.
Business Central OneDrive Cloud Storage Integration
Stefanetti shares another “what’s new” feature with the OneDrive integration with Business Central, making it easier to access and modify documents.
Why Publishing an App Uses So Much Memory
Matt T offers: “Random tip of the day: Sometimes publishing an app just eats up a lot of memory. I would love to know how publishing an 18MB app file can use 6GB+ of memory (or would I?). Needless to say, if you ever run into OutOfMemory exceptions when publishing apps to your containers, don’t forget you can change the memory limit in the scripts\settings.json file. Every so often, you might need to up this beyond the default 6GB.
{ “memoryLimit”: “10G”
}
Tom replies: “Not that I’ve run into this issue, but I have to wonder if restarting the container wouldn’t help alleviate the issue.”
Matt responds: “It’s actually part of the create container process … installing all the dependent apps.”
Vendor Remittances in the ACH Process
Leanne is looking for assistance: “Good Morning! We have an upgrade customer that will be using the ACH functionality in Business Central SaaS. The Vendor Remittances will be emailed. In the ACH process, this happens before the file is generated and sent to the bank. The customer would prefer to send the remittances after the file has gone to the bank and is approved. Has anyone found a way, without a mod, to “queue up” emails and send them later (maybe via a job queue)? I did some research on this but didn’t come up with anything. Thanks in advance!
David replies: “Nope, and I still have no idea why they (Microsoft) think sending a remittance prior to bank acceptance makes any sense.”
David comes back: “I thought a bit more on this, and there might be a workaround. If I recall, there is a feature to bulk send the remittance in the journal and a feature to resend a remittance advice from the ledgers. So, in theory, you could generate the remittance to pdf (or anything other than email), process the files, and then use the resend function to send the remittance, or generate the files, don’t post, and once accepted, run the bulk send and then post. You would need to test the flow, but this might work without code.”
Leanne responds: I’ll check this out. Thanks David!”