Last week I was preparing a new How Do I video about the integration of Microsoft Flow with Microsoft Dynamics NAV 2017. As you might know Microsoft Flow is a platform were you can easily integration between other systems like Twitter, Facebook, Mail, … . You can find some more information on
I think the following scenario will sounds familiar to every developer.
You develop a nice new feature with a couple of tables, pages and codeunits. These new objects needs to be imported in the production environment.
You make a fob file of all your objects or create deltas, import it in the development environment and compiles the objects. And maybe you need to restore the NST, but this is questioned many times. Some are saying this is mandatory but I doubt it.
Before your solution will work, you need to do some setup in every company by opening the pages and provide the right parameters. A very time consuming (aka monkey task) to do and if your head isn’t clear you can forget something or make mistakes.
Would it be nice if the system itself will know when there are objects imported and auto configure your solution? That the system will raise an “OnAfterObjectsChanged” event the first time you open a client after you imported you objects.
That is what I’ve created and I will share it with you in a moment.
The first part is to determine if there are objects imported to the system. As you properly know these are created and updated in the system table “Object”.
Now I need to know when this table is changed from within NAV itself.
First, I thought to use “OnAfterInsert, OnAfterModify or OnAfterDelete Events” on this table, but these will not be raised from within the development environment when you import objects.
But then I come up with the following idea.
As you might know there is a field called “Timestamp” in every NAV table. This is maintained by SQL on every insert and update.
So, if I make a sum of all the timestamps in the “Object” table and compare it with a previous saved value, I know that something has changed and even that there are records deleted!
To get the sum of the timestamps, I used the following SQL statement and executed from within NAV itself.
Factboxes are more then ever a powerfull way for presenting related information. Normally you link your Factbox through properties, but now and then you need to do this from code.
This works fine if your page has at least one record, because the filtering is set on the “OnAfterCurrRecord” trigger of the page. So when there is no records, no filter is set on you factbox and then all related records are shown.