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.
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
Estimated Level of Effort:4-8 Hours of Model Building Level of Difficulty: Beginner Recommended Training: L2 Model Builder Training Persona: Casual Model Builder Potential ROI: Decreased planning time Increased accuracy of targets/spreads You Might Also Like: * Historical Snapshotting Top-Down Allocations Whether it's…
This item has been identified as an outstanding known issue. A workaround is provided until the issue is officially fixed. Issue For versions 1.6, 1.7 and 1.8 of the PowerPoint Add-in elevated privileges are required to install the add-in through command line and for the "all users" option. Workaround * Installing through…
