Part of the query on cmdb ci has been ignored because of insufficient access query range operation

pradeepcm
Tera Contributor

3 weeks ago

Hello Everyone ,

 

@crowe1288greg   @AndersBGS  @nitin gupta1  @Dr Atul G- LNG  @Tanushree Maiti

 

 I'm seeing the following message  when creating a new change Request in UAT instance .

 

part of the query on cmdb ci has been ignored because of insufficient access for query range operation on cmdb ci attributes .

 

The message appears immediately when opening a new change record even before selecting a configuration item,.

 

 

I would appreciate your guidance on the above 

 

What typically causes this query range access message on cmdb ci attributes ?

 

Is this usually related to ACL data filtaration , query business rules or cmdb applications ?

Has any one encountered this after a platform upgrade or patch?

 

What logs or troubleshooting steps would you recommend to identify the root cause ?

 

Any suggestions nor similar experiences would be greatly appreciated .

 

Thanks and regards ,

PradeepM

0 Helpfuls
  • 348 Views
1 REPLY 1

J Siva
Kilo Patron

3 weeks ago

Hi @pradeepcm 

  • Check whether any on-load Client Script or UI Policy on the Change Request form is attempting to populate or set the Configuration Item.

  • ServiceNow periodically introduces query_range ACLs on tables that meet specific criteria.
    A query_range ACL can be applied at the field level and is triggered whenever a query is executed against the table using that particular field.

Regards,
Siva

0 Helpfuls