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.
Just like the main question above, I wanted to try out the new feature on the board where you can you the insights panel to put additional cards. However, I wanted to synchronize scroll a card on the main board with the card on the insights panel but I can't find where it might be.
Hi everyone, I am trying to create a connection ADO from PostgreSQL, but I consistently receive the following error: Failed to establish a connection The following message was sent from the target system: The SSL certificate is either invalid or not in unencrypted PEM format. Please check your certificate and try again.β¦
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-yearβ¦
