Just one example: I have used that in a customer report for collecting countless unsorted serial numbers, sorting them at runtime for a neat consecutive printout, using the temporary table as a dataitem.
Can ease your life as a developer on quite a number of occasions (in all NAV versions, I first saw that being used in 2.01 )
It does have some drawbacks too, if your customers do their own development work, as they will sometimes stumble upon these tables:
- when they try to export modified objects for a source code merge to reconcile the production database with the test database
- when they try to modfiy objects where you have used these unlicensed tables
since these are not included in their license.
You can use any table as the source for a temporary record variable, whether you have it in your license or not. Used that way it's really just a programming construct, not an actual table.
And that temporary table that you're using is a customized table outside of the range of customer with the desired key you want?
Exactly . In my case both key and field structure were needed to give the document the required good looks.
Just for sorting , you could use any table with an approiate key as a temporary instance , but always make sure that it really is "Temporary".
In case you forget to set this property, the usual DELETEALL on a table with records within the license range will have disastrous consequences, so it is safer to use tables outside of the license range.
Comments
Tino Ruijs
Microsoft Dynamics NAV specialist
Can ease your life as a developer on quite a number of occasions (in all NAV versions, I first saw that being used in 2.01 )
It does have some drawbacks too, if your customers do their own development work, as they will sometimes stumble upon these tables:
- when they try to export modified objects for a source code merge to reconcile the production database with the test database
- when they try to modfiy objects where you have used these unlicensed tables
since these are not included in their license.
And that temporary table that you're using is a customized table outside of the range of customer with the desired key you want?
I think I get it.
Tino Ruijs
Microsoft Dynamics NAV specialist
RIS Plus, LLC
Just for sorting , you could use any table with an approiate key as a temporary instance , but always make sure that it really is "Temporary".
In case you forget to set this property, the usual DELETEALL on a table with records within the license range will have disastrous consequences, so it is safer to use tables outside of the license range.