Pages with 2 models as a source has issues with Actions. A major problem

DeveloperCYT

We have a new page with 2 model sources, and an action button from each source.
When we select the first model 'CyT - DATA HUB', we see the 'UPDATE SUPPLY CHAIN' action greyed out as expected, as it is from another Model, and cannot be pressed.

The action info is correct (highlighted) for the DATA HUB 'IMPORT ORDER' action.

Then we switch to the 'SC 01-05-2025' Model
The action from the DATA HUB is NOT greyed out as expected, and is active BUT now has a different action in the info (highlighted), but the same label.

I am assuming that it uses a #ref for the action, and this happens to be that #ref from the SC 01-05-2025 model.

This will cause issues if the user clicks on the IMPORT ORDER button in error, as it will try to run the incorrect action!!

This is a dangerous hidden issue, with multiple source UX dashboards.

Is there a way to stop this happening?

seb_mcmillan

Hi

This isn't really what the linking pages to multiple models was intended to do. Though you can link the same page to multiple different models you will find many of the cards won't work, e.g. a grid can will break if the underlying module in one model doesn't exist in the other model. 

The functionality was introduced to provide an ALM for UX where each of the linked models is structurally the same e.g dev, test and prod versions of the models. This means you don't have to replicate and maintain the same pages for each of the ALM models. This is also why you can both save and preview or publish pages as it means you can update and test pages for dev without pushing them to end user before you are ready.

I would have these actions in different pages each pointing at the right model.

Depending on exactly what you are trying to do you could potentially look a using a workflow.

Hope this helps