@Mikolaj_Zielinski It looks like the account that you are using doesn’t have access to most of the ServiceNow objects. Maybe the admin can control what’s visible, readable, editable etc. by the users in their account? So, can you also check with your Admin, whether you have access to these tables or not?
You can also check by logging-in to the servicenow site and check if you are able to view these tables and if you are able to read those table’s content (as shown in the screenshot).
Also, the ServiceNow tableNames are fetched dynamically in the activities i.e. they are fetched at run time based on the account’s access/permission. Hence, you should be seeing those tables only if you has
ws_access on them and only if they are not views. The vendor API returns all the tables from
sys_db_object and we are filtering out
views and tables that don’t have
ws_access . Hence, if you can share the metadata of 1 table that you are trying to access from the data dictionary
sys_db_object then we can compare it against our sandbox to determine the root cause.
Otherwise, an alternative approach would require us to first check the logs in order to see how the API request is being made to ServiceNow. For that, you would have to share a very recent Request ID.