Archiving function

The archiving function reduces the amount of data in the TRS manager making it easier to manage and keep only “fresh” and up-to-date data in the system.

Open

How to start using the archive function?

You activate the archiving function by changing the setting ArchivingKeepMonths, which can be found on the settings page (on the cog wheel in the top right corner) or you can talk to the support and we will activate it for you.

Open

Default the setting is set to zero months which means that you keep all transactions and no transactions are archived at all. 1 month is the minimum, which means that you will keep 1 month of original transaction data and all other transactions are moved to the archiving storage. We recommend that you keep approximately 2 years (24 months) of transaction data, which will give you a sufficient buffer for easy access to recent transactions.

How does it work?

If you have the archiving function activated (more than 0 months in the setting), a background job will run each Sunday removing transactions and their related data from the storage used today and moving it to a new storage. By doing this we reduce the data that are stored for each transaction to the minimum required and still not compromising functionality.

Will I lose the data completely?

The data is not completely lost from the TRS Manager, it is still stored in the files, so if you need to access data from further back than the month you keep the transactions it will be available in the files reported to and/or received from FSA, which can be found and downloaded in the TRS Manager application.

Cancellations

Even if the transaction data are reduced to the minimum it is still possible to create cancellations from that data. When a correction is made in the Bricknode system the TRS Manager will be able to produce a cancellation transaction from the archived data and send it to FSA. The archiving function will store the required amount of data needed to be able to create cancellations and send them to FSA.