Insufficient rights to query record

[ChrisGetint]

Hello ServiceNow community!

I'm an integrations consultant for a product that integrates Jira to ServiceNOW.

We have a process so that our users can create a dedicated ServiceNow user, and integrate ServiceNow to Jira with our tool based on the credentials from said dedicated user.

For this user, we created a specific role that has read permissions to the following records:
Dictionary Entry [sys_dictionary] - *
Dictionary Entry [sys_dictionary] - None
[sys_glide_object] - *
Choice [sys_choice] - *
[sys_glide_object] - None
[sys_journal_field] - None

The dedicated user also itil role.

The problem we are facing right now is that we added a SPM (Strategic Portfolio Management) module to our ServiceNow instance, which allows us to create Projects and Project tasks work items.

This user is unable to create Projects or Project tasks, when we try to create Projects or Project Tasks through the integration tool we experience the following error:

Failed to fetch sync triggers: Invalid response status code received (expected: 200 but got 403). Response: {"error":{"message":"Insufficient rights to query records","detail":"Field(s) present in the query do not have permission to be read"},"status":"failure"}

The error indicates that there are fields in the integration that can't be read, however the only fields I'm trying to integrate are:

Jira Title [Summary] - ServiceNow short description
Jira Description - ServiceNow description

Does anyone know what could be the problem? Maybe the role is missing some records, or the user is missing some roles?

Thanks!

[ChrisGetint · Accepted solution]

Hello guys, I was able to properly fetch projects table and circumvent the issue, 4 extra records needed to be added to the role we created for the dedicated user.

Thanks!

[vv6]

Hi Chris, I'm getting the same issue when trying to fetch parent record via API

Get :  /table/wm_task?sysparm_query=parent.u_id%3D558086&sysparm_limit=1

'u_id' is  a custom field on the parent table. The ACL's seems to fine has read write update for the user. When we directly query the parent table it seems fine with the same field. What is the solution that worked for you.

{
  "error": {
    "message": "Insufficient rights to query records",
    "detail": "Field(s) present in the query do not have permission to be read"
  },
  "status": "failure"
}