The real performance load happens when:
Each entry inserts a record into Dimension Set Entry, and dimension set IDs need to be generated.
Having 1000+ values is fine — but having millions of dimension combinations can slow down dimension set creation.
When queries apply:
Dimension filters
Grouping on dimensions
…it means extra joins on G/L Entry → Dimension Set Entry.
This is still OK, but performance depends more on:
If you expect heavy posting volume and large number of dimension combinations, follow these best practices:
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
OussamaSabbouh 3,106
Jainam M. Kothari 2,291 Super User 2025 Season 2
YUN ZHU 2,010 Super User 2025 Season 2