turn off subsidiary view in module after "version" is added

Hi All,

I was wondering if anyone might have experience in this issue I am having. I built out a few modules and am now realizing that I need to add the versions dimension to a few. However, when I apply the versions the module changes to a subsidiary view and therefore eliminated the ability for data to be manually inputted without clicking into the "old view."

Is there any way I can add the Version Dimension while still keeping the functionality I had prior?

Accepted answers

zafkamar

Hi Mike,

The other way to do this in the existing module is to take a look at each line item in the Version field. If you only change the dimensionality of the module but not of the line items, then those subsidiary views will persist. Try copy-pasting the selection of 'All Versions' (or whichever version selection you've elected to go with) to the other line items. That ought to take care of the subsidiary view.

Zaf

All comments

rob_marshall

Mike,

It turned to subsidiary view because the dimensionality of those line items are not the same as the definition of the module. I would recommend to do the following:

create a new module with then new dimensionality (versions added)
and then link this data to the "old" module. When you are playing with versions, you will need to use the SELECT. So your new formula in the old module will be some thing like this: new_module.Data[SELECT: Versions.Actual]

Thanks,

Rob

zafkamar

Hi Mike,

Zaf

mingrassia326

Thanks Rob - as always very helpful! I appreciate the guidance.

mingrassia326

Zaf, that's actually exactly what I was looking for. Thanks so much!

zafkamar

Right on - glad I could help!

Quick Links

Can you help?

Unanswered questions

how to count how many times an action has run?
I want to create a line item which will increment by 1 every time an action is run manually. This action is an import which doesn't involve any file upload to anaplan. The module where I want this line item has users list & SKU list dimension. No time. So basically, I want to track how many users have selected an SKU and…
Missing Column Headers in Anaplan Export When Using API
Hi Community, I’m encountering an issue where an export created in Anaplan is missing column headers when retrieved via the API. However, when I manually run the same export from the Actions tab, the downloaded file includes the headers. Has anyone experienced this behavior before? I’d appreciate any insights into the root…
Importing from Data Hub: Incorrect or Missing Mappings in Target Model
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…