Today we do not have the ability to define a table of temporary nature that survive across sessions. This would be very useful in cases of integration where the connection to BC is stateless in nature but where lookup of data or data exchange is not.

Having the ability to create a table that is only usable and existing in server memory until next application server restart or Record.Delete(All) and that does not touch SQL Server, would enable the creation of processes and integrations and what-not that depend on saved state but only temporary data.

The solution would also perform better since the data does not touch SQL Server. The table itself would behave the same way as a regular table.
Category: Development
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team