UI policy on table in a different scope

[Jon Barnes]

Does anybody know why I can't select a table from another scope when creating a UI Policy? Consider this scenario:

I have Scope A and Scope B

Table 1 is in Scope A.

I create a view of the Table 1 form in Scope B.

Now I want to create a UI Policy in Scope B specific to the view I created in Scope B. But I cannot select Table A in my UI Policy.

[scott barnard1]

Hi Jon

Are they 2 scoped app tables or is one a scoped app and the other Rhino?

Regards

[Jon Barnes]

There is only one table in question, and it is in a scoped app, we can call it Scope A. Within Scope B, I created a Form view of that table. But I cannot create a UI Policy in Scope B on the table that is in Scope A.

[scott barnard1]

If you go to the table record of the one table and go to the application access tab, what do you have set.

I just tried it on one of mine it it didn't work either however I do not have the allow configuration checkbox marked true.

Could be worth a doc search on app access.

Regards

[Jon Barnes]

I have all of the checkboxes checked. I also noticed I can't set a field mandatory in a Scope B client script on a Scope A table. Not sure if there is access I can grant for this or if this is simply not allowed (UI Policies, and setting mandatory/read only, etc from a client script) across scopes.