The obvious current solution is to make note of the model size before and after syncing changes, but adding change to model size in the comparison report would just be a great QoL change, especially for model performance reporting purposes.
Be sure to add this to the idea exchange for consideration in future Anaplan roadmap: https://community.anaplan.com/categories/ideas
@jzink1211 : Are you referring to the comparison report between 2 revision tags? Nice idea :)
Indeed it would be a really nice and useful tool, but I think it would add a lot of need of calculations to identify the impact of the structural modifications that generate a size impact in the model (add line-items, add elements in lists not flagged as production data).
Maybe it would be possible to create a special report or something :)
@alexpavel
Yep. Exactly. Just between two revision tags. I guess I thought there might be snapshot data of model size in the backend but perhaps it gets overridden once a sync goes through? I thought there might be a way to pull model size from the meta data of a model at different points in time and simply calculate the difference? But I'm not sure what that looks like in the backend.
There was an error rendering this rich post.
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context andβ¦
