I’m currently working on a new app (for AppSource) and I need fast accessible information throughout a user session that I can look up without having a performance impact on the user experience.
Very often when developing we have logic we would like to execute on records, but only when the table is actually a real table and not when used as a temporary record. This could be things like inserting, modifying or deleting attached records in another table which would make no sense in most cases if the table you are currently in is temporary.
Temporary datasets are a widely used feature across the Dynamics NAV application. Examples of potential uses include reports, pages (e.g. the Navigate page) and queries. Temporary datasets can be represented by a so-called “buffer” table which is loaded with values and then used for further processing. Of course, the end-user will not see the difference in the data representation, be it from an existing table in the database, or from a temporary dataset holding the values from multiple tables.
Boy, have these last months been busy.
Now I am working on a management solution for our cloud offering. This solution is going to give the control of the services and the tenants to a NAV user interface. I am running Powershell scripts from NAV (thanks Waldo) and things are looking good so far.