It is possible to set transaction drill-through specific to a version by associating transaction reports with a version. This becomes possible when:
- An Admin designs a transaction table so that data can be partitioned into sets that map to a version. A column called Encumbrances, for example, can be created in the transactions table. If a record in the transaction table is an encumbrance, it could be marked with a Yes in the Encumbrances column.
- An Admin prepares multiple transaction reports - one for each version that needs filtering. As an example, they create an actuals transactions report which gets filtered by No in the Encumbrances column, and they create another transaction report that filters by Yes in the Encumbrances column.
- An Admin associates these reports with their corresponding versions. The actuals transaction report, for example, would be associated to the actuals version by navigating to Modeling > Model Management > Versions and using Drill into Transactions option to browse to the shared Transactions Report.
- The end user visits a sheet for a version, actuals, for example, and invokes "drill into transactions" within a sheet. The drill into action then draws on the transaction report for that version.
Version Specific Transaction Drill-through does not apply to NetSuite drill-through, and is only visible with the transactions module. If a version with this setting gets cloned, the setting goes with it. The default setting for Drill into Transactions uses the raw transactions.