If a client has finalized a dataset in Active Ledger or has not updated their trial balance (TB) for a binder in Active workpapers, why do additional new transactions appear in Active Workpapers or Ledger, even though the client hasn’t clicked 'Load Data' or 'Refresh Trial Balance'?
Active Ledger:
If 'Load Data' is not clicked in a dataset, but a report (such as a Ledger report) is generated with the API Transactions option enabled, any additional/new transactions will be imported. These transactions will be reversed until 'Load Data' is clicked.
Active Workpapers:
Transactions are imported into Active Workpapers (AWP) when the General Ledger (GL) for an account is viewed with the API Transactions option enabled OR if a GL workpaper is used. This will bring in any additional/new transactions, and will show an out-of-balance as the totals does not match the existing TB account balance.
Active:
When any columns are edited within an Active Workpapers binder, Both:
i) the dataset in Active Ledger loads with new data and transactions
AND
ii) the binder is refreshed with new transactions and Trial Balance (TB) account balances.
Please refer to the attached video for further details: Edit Columns in AWP loads fresh data into dataset.mp4
Cause: This is by design and expected behaviour. Accurate and updated transactions can only be queried and imported from the source file via its API when one of the features mentioned above is used.
Here are the Feature requests logged in relation to this:
lock datasets;
https://businessfitness.atlassian.net/browse/PD-52
compare/reinstate:
https://businessfitness.atlassian.net/browse/PD-349