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.
Test - Please Ignore
Hello folks, Does anyone know how to work around the Polaris limitation of using the Formula or Ratio summary method alongside the Closing Balance within the same line item? I have a Business Unit list where the total (All BUs) must display the Corporate (1 of 20 leaf items under All BUs total) number of Unique Customers.…
Has anyone found success using Anaplan XL with Polaris models in a shared drive with or without concurrent users? My team has experienced a variety of errors, login failures, etc. sometimes it works, sometimes it doesn't. We've been recommended to save and edit files locally, which helps but certainly with its limitations…
