Read operation on table 'sn_hr_core_case' from scope 'Global' was denied. The application 'Global' must declare a cross scope access privilege.

[Beno_t Proulx]

I have a Service Portal Page that uses the out-of-the-box "Data table from instance definition" widget to display records from the sn_hr_core_case table. I am running this on Paris version.

However, it does not work because of some scope issue which don't seem to make sense to me since it says it's denied from scope "global"... Read operation on table 'sn_hr_core_case' from scope 'Global' was denied. The application 'Global' must declare a cross scope access privilege.

So I am somewhat puzzled... I tried to query form another table and I was successful in retrieving records from the sn_hr_le_table without the cross scope problem. I have not tried other tables than that so far.

A search from Google revealed that there was the same issue (or seems very similar) that was fix in London's version.

https://docs.servicenow.com/bundle/london-release-notes/page/release-notes/quality/london-patch-7.ht...

Anyone else can replicate the issue? or may have a solution or workaround to propose?

[Ashutosh Munot1]

Hi,

Add the cross scope application entry

Thanks,

Ashutosh

[Christian Prob2]

So this is - imho - the obvious quick&dirty fix. I would really like to understand why this is not an issue in the ootb configuration and why the ootb configuration does not really need any cross scope entries between HR and global.

That makes me think I should not need those either in cases as Benoît pointed out.

One of the main reasons to have the whole scope separation is security, so if i blindly just add Cross Scope entries that kind of defeats the purpose and may put security at risk, or am i missing something?

Christian

[Beno_t Proulx]

Thanks for taking the time to respond.

However, as I'm mentioned the system does not allow to create a cross-scope record where the source is Global.

So I tried the opposite (although it does not make much sense to me) and as expected it did not impact the result:

[Ashutosh Munot1]

Hi,

Which table you are trying to refer using HR Scope to Global Scope.

Because When you are creating the cross scope record in target name put GlideRecord.update , GlideRecord.setValue etc.

Thanks,
Ashutosh