Composite hierarchies List and Production Data

hugobarata

Hello Everyone,

I recently took over the model development from a previous team, and I'm looking into optimisation options.

One issue I came across has to due with Composite hierarchies List used for Selective Access, as per the example below:

G1 Group - Used for Selective Access - Set as Production Data - No changes in data

G2 Country - G1 Child - Used for Selective Access . Set as production Data - Possible, but very limited changes.

G3 Entity - G2 Child - Not used for Selective Access - Set as Production data - Possible, but very limited changes. Is used in several subsets that require a lot of maintenance.

I understand that G1 and G2 need to remain as Production Data, since they are use for Selective access. However, changing G3 to Non-Production data, would not only reduce the subset maintenance required, but is would also reduce several issues we have faced when maintaining the subsets between different modules.

I understand that additional maintenance would need to be setup in the spoke modules to guaranty composite hierarchies accuracy, but I'm trying to understand if there would be any additional drawbacks on changing G3 to non-productive data (apart from re implementing the ALM process base on the Updated Production Model).

Thanks in advance,

Hugo Barata

SriNitya

Hi @hugobarata
If you are planning to change G3 to Non-production data, then parents for the list G1 and G2 will be unset as production data. Below screenshot appears when you change the production data mapping.

Hope it helps
Thank you

hugobarata

Thank you. Yes, I tested that on a dummy model after I posted my question, and I did get the same issue.

So that us out of question.

What I did found in the same dummy model, was that, even if all members were change of composite hierarchy were change to Non-Production data, the Selective Access for this list, seem to work as normal.

I had a similar issue when I was working with another client before, and at the time, the Solution Architect on the team mention that if a List is to be used for Selective Access, it need to remain a production list.

It would be great to understand if the statement above regarding Selective Access is accurate (my tests on a dummy model, seem to indicate that this statement is not accurate).

Thanks in Advance,

Hugo

seymatas1

Hi Hugo,

If a list is to be used for selective access, it needs to remain a production list

This statement is not accurate. There isn’t a restriction in the UX pages that prevents you from setting up selective access for a list.

What I think your solution architect meant is this:
When a list has selective access enabled, its access permissions are treated as production data.

Production data refers to objects that can be modified in a production model.

For example:

• In the Users tab, you can add users directly to a production model without adding them to the development model.

• In Time, the Current Period is considered production data, so you can change it in a deployed model.

When you enable production data for lists, imports, or import data sources, you allow these objects to be updated directly in production models.

I hope this helps.

Seyma Tas 🌷🙂

SriNitya

Hi
If a List is to be used for Selective Access, it need to remain a production list → this statement is not true.

hugobarata

Thank you Seymatas and SriNitya,

Both your comments were super helpfull.

I will take into consideration, the addition effort that it may be require to maintain both the our Composite List structure as well as the corresponding selective access when analysis the best solution for us in terms if implementation.

From it seems that the major road block I was facing was actually related with the need of selective access list required to be production data (the project where this happen was already more then a year ago, so I may be missing other client specification that lead to this comment/decision by the SA at the time).

Thank you so much for your support.

Best,

Hugo Barata