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.
Hi! In London it was mentioned, any update on this?
We've been building a tool called aplan4sheets and we'd genuinely like input from this community — both on what we've built so far and on what we should prioritize next. The problem we set out to solve: Anaplan's Excel add-in is Windows-centric, and there's no real native way to pivot Anaplan data in Google Sheets. We…
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.…
