A common challenge in many business management applications is avoiding unwanted changes in data. It could be anything from an incorrect customer name to an incorrect posting to the general ledger. In this blog we will summarize how to Monitor Changes in Dynamics 365 Business Central 2020 release wave 2. There are currently three ways.
This topic is probably as old as the RTC client. If you want to display a text field on a Page you will try for around two hours and then you will give up and maybe build a control addin to solve this.
In the web client this problem was not solved by now. We have fields with length up to 2048 but we are not able to display this.
Today I was working on our ForNAV AppSource App and I decided to clean up some of the warnings that were introduced with BC16. This was about converting Options to Enums and vice versa.
Converting an Enum into an Option is easy. Just add ToInteger() and you’re done. But how about the other way around?
I’m not a big fan of using BLOB fields on the Dynamics 365 Business Central database, but there are many scenarios where you need to handle BLOBs inside the database directly.
As an example, imagine to have an application that handles different types of labels related to items and these labels are stored inside the Dynamics 365 Business Central database in a table called Labels. This table is defined as following:
More than an year ago I’ve written this post explaining how to handle breaking schema changes on a production Dynamics 365 Business Central SaaS tenant. I think that every Dynamics 365 Business Central developer now knows that in a production environment you cannot remove objects or fields (breaking schema in the database) but all schema changes must always be additive.
For long, we (as a partner community) have been asking for longer field lengths. And this time, Microsoft seems to have delivered: about 860 field lengths were changed. Mostly from Text50 to Text100, but also from Text30 to Text50 and so on. For your convenience, I created a csv on my “CALAnalysis”-repo on github that lists all of them.
This is a great blog post to write. A long time ago I bitched about the artificial limit we still had, inherited from the old native database. Read it here for a quick refresher https://www.hougaard.com/nav2017s-inheritance-from-the-native-database/
Luckily for all of us, Kennie https://twitter.com/KennieNP from Microsoft actually reads my blog and with the April’19 release of Business Central two of these limits are now removed: