Error after switching Data View to a different Data Model when "Multiple Data Models" is enabled

Question

Hello,

I would like to clarify whether the following behavior is by design or a bug.

Scenario

A screen is initially configured to use Data Model A. The "Multiple Data Models" option is then enabled. Afterwards, the existing Data View is changed from Data Model A to Data Model B. Immediately after changing the Data View, an error message appears:

Even if the screen itself is subsequently switched to Data Model B, the error message still remains.

The issue occurs when testing with a Power User license. The issue does not occur for Developers. The affected Power Users have a database security profile granting access to both Data Model A and Data Model B.

Is this behavior expected and therefore by design?

Or is this a product defect/bug?

According to the users, this scenario reportedly worked in Board 12 in the past.

Therefore, we are unsure whether this is an intended change in behavior or a regression.

Thanks in advance for your feedback.

c.rudolph · Answer

Thanks, yes, there is an error in the diagnostic log showing “CannotAccessResource” / “Access Denied.”

Interestingly, this even happens with a completely empty Screen and an empty Data View, so it’s still unclear to me why this appears to be a security-related issue.

I’ll discuss this with our service provider and see if we can identify what is causing it.

Thanks again for your help!

Robert Barkaway · Answer

Okay that's useful, in theory as long as the Power User has the same access on model B then it should be able to repoint it I'd think, I can only think that something in their security restrictions is causing it a problem when it tries to actually switch the layout and any layout selections to Data Model B, something which is no longer an issue once it's been repointed. Are there any layout selections that it might be having trouble transferring? Also have you checked the Diagnostic log to see whether it shows anything there (I'm not sure whether it would or not but worth checking)?

c.rudolph · Answer

Hi Robert,

I tested your suggestion. If I repoint the Data View to Data Model B as a Developer and save the screen, the Power User can open it afterwards and use everything without any issue.

If the Power User tries to do the same repointing themselves, however, the error appears.

One clarification: the two data models are not identical and the security permissions differ between them. The Power User does have access to both, though, and can use the Data View in Data Model B after it has been repointed by a Developer.

So the issue seems to be specifically related to the Power User performing the repointing rather than accessing Data Model B itself.