Ledger Agent querying context limitations
Ledger Agent shows with my org's GAAP ledger set as it's default ledger/ledger set context. This ledger set contains 17 ledgers, however, when querying balances and journals the subsequent context that the agent shows to have applied to my query is the first 10 ledgers, in alphabetical order, with the last 7 being dropped. As a result I am returned incorrect answers as the query I have submitted is reliant upon having complete context.
What needs to be done to dynamically consider the appropriate 17 ledger context? Is there a cap on the number of ledgers being considered that can be changed?
Tagged:
0