Invalid Analytics Model - No mapping attribute found for dimension

[PMathieu]

Invalid Analytics Model - No mapping attribute found for dimension

This issue is done by the last SAP Datasphere update (09/01/2025 - 22/01/2025) - Note 3560510

1. It is important to have an unchanged copy available or (in production for example) because it is necessary to be able to find the technical dimensions and names used before the update

2. Identify associations with problems, Error messages in the analytical model direct you to the problematic dimensions

Here it is the Time-dependent Equipment dimension which comes from the Time-independent Equipment dimension

The entire branch needs to be redone
3. The original branch must be deleted, in order to be able to rename the new branch. So it's important to have another model available as a reference.
4. Select the Node N-1 of the problem node and you will find in the list of fields the available dimensions (associations)

The problematic dimension should be there, but not checked

5. Check the dimension and click the arrow on the right to go in. Here, tick 'Use associated dimension'

6. Go back a step and change the technical name of the dimension to the original.
This name is also the name of the association in view n-1

Technical name adapted in the analytical model:

The technical name of the association in the Equipment (Dimension) view, the original dimension of the problematic dimension:

7. Click the pencil next to the attributes and choose 'None' for the technical name. Otherwise the technical names of the fields change back and the reports will no longer find them.

It's a major part because this technical names on attribut have an impact on your SAC report ! 

Be careful that if in the past you had defined a suffix or prefix, you must put the same one back (see your AM prod)

8. Now you can add the fields of the dimension. Also reference an unchanged template to check if the description has not been changed.

9. Repeat for the rest of the branch and for other problematic dimensions.

Note, in Production at the level of SAC reporting, we don't see the impact of the Datasphere update because the AM works on the basis of the deployed version but once you want to redeploy it it will be wrong.

By Jorg Vandersteen