No data format line items, considered still in size estimation before Sync to PROD?

AndreeaCepoi

Hi all,

Have you ever encountered the situation of first not being allowed to sync to PROD due to over size of workspace limitation ( sync blockage message was showing an increase of PROD with 30%, which was over max size workspace 130GB), but at second trial, after deleting a module with No data format on all line items (0 cell counts) to allow you to sync (PROD model increased with only 3 %in fact) ?

Module that i deleted to allow me after the sync, was dimensioned on one subset of a 4th level of a hierarchy and one flat list, Time (weeks) and had No data format on all line items.

So, is it possible that the oversize warning blockage message of sync is considering also the No data line items?

This sync blocking message i got last Friday, 4th of April 2025

Thanks,

Andreea

edna23roe

Hello Andreea,

Yes, it is absolutely possible that the oversize warning blockage message for syncing to PROD was considering the module you deleted, even though it had "No Data" format on all line items and zero cell counts.

Here's why:

Metadata and Structure: Anaplan models aren't just about the data they hold. They also store metadata, which includes the structure of modules, dimensions, lists, line items, formulas (even if they result in no data), and formatting. This metadata contributes to the overall size of the workspace.

Module Definition: Even a module with "No Data" formatted line items still has a definition. This definition includes:

The dimensions it's built upon (your subset of the hierarchy, the flat list, and Time).
The line items within it (even if they have no data format).
Any formulas that might be associated with E-ZPassMD those line items (even if they evaluate to blank).
The overall structure of the module itself.
Workspace Size Calculation: Anaplan's workspace size calculation likely takes into account the total amount of storage required for all the structural elements and metadata within the models in that workspace, in addition to the actual data being stored in cells.

Impact of Deleting the Module: When you deleted the module, you removed all of its associated metadata and structural information. This reduction in the overall structural footprint of your development model likely brought it below the workspace size limit, allowing the subsequent sync to PROD to proceed even though the actual data increase in PROD was only 3%.

AndreeaCepoi

Thanks @edna23roe

That makes total sense, i knew the lists are occupying also size in the model (500b per item), which does not show in line items cell counts, but i thought cell count of a line item showing 0 would mean no model size impact, will take that into consideration from now on.

Thinking now also to be careful with No format line items used to give a visual structure to the model between modules and line items ( ===DATA== ,INPUT=== , ===CALC=== , TECH=== etc.).

To mention, that what surprised me was also was the 30% increase estimation before sync, while the subset and the flat list were existing already in the model before the sync and the module was containing max 5 line item of formulas, rest of them (40) were no formula as wanted to import into that module a snapshot report (copy data calculated from another module)