Dear Experts,
Are there options to create a model with more than 130gb size?
The maximum size of a single workspace is limited to 130Gb. Therefore, it would not be possible to create a single model that exceeds 130Gb. Instead, you would need to build multiple models within multiple workspaces to accomplish this.Maximum workspace size is controlled by the infrastructure that the Anaplan platform operates. Any one Workspace does not exceed 130Gb. Within a 130Gb workspace an individual model could consume the entire Workspace. Note that model performance is effected by variables such as data volumes, concurrent users, calculation complexity and other factors of model design in addition to model size. These variables need to be considered along with the model size. Model size is generally estimated based on the number of cells within a model at a ratio of approximately 10 bytes per cell. Hence a model is limited to a range of 10-12 billion cells in order to fit within a single workspace.Please feel free to reach out to your Customer Success representative to discuss your organization's options and goals.
Thanks Mark.
Quick question...Can the system determine the Sparse cells and optimize the models every time data is saved so that sparse cells don't occupy the space?
Cells which are sparse (i.e. not populated) are not handled any differently that populated cells, the model treats all cells as if they will be populated either by input or formula.
When importing data from a Data Hub to another model, I'm seeing values in the target model that don't exist in the source. For example, seller assignments are being tagged with subregions that aren't present in the source data - some assignments are missing expected tags, while others are mapped to seemingly random…
Hi, I need help in pulling a specific view in Anaplan XL. The first grid should display attributes of various projects, while the second grid should present the monthly financial data for these projects. Thanks in advance.
Hi, I am working on a solution where the User should only have access to write/edit the list members that they add from an Action on the frontend. This action adds another list member to a selective access list. The problem is, in order to run the action, you need access to the entire list, so you would see all list…
