"sys_dictionary" table missing column entities for some system tables

[Gowtham Rajkuma]

Hi,

I'm new to Servicenow and facing an important issue which is impacting our integration. As mentioned in the Servicenow documentations that "sys_dictionary" table carries information about all the tables and each column of every table that exists in service now : https://docs.servicenow.com/bundle/sandiego-platform-administration/page/administer/managing-data/concept/c_DataDictionaryTables.html.

But I'm noticing that some columns are missing from `sys_dictionary` table (Both from API and when I access via Portal). The columns exist the table, I can fetch the list of columns via api and it's showing in the portal as well, but when I'm fetching the list of all columns against the provided table name, some columns are missing. 

This is how I'm making the API call:

`https://<instance-name>.service-now.com/api/now/table/sys_dictionary?sysparm_query=name=change_task&sysparm_fields=sys_name,name,sys_id,element` - it list the table along with all the columns of this table, But noticed missing columns for two system tables so far, `change_task` (Missing column : `additional_assignee_list`) and `text_search` (Missing column : `sys_tags`).

Can anyone please tell why the sys_dictionary table is missing these columns, even though it's there in the schema of the tables. Am I missing any parameter in the api call that needs to be included? 

Kindly let me know, Thanks.

[Allen Andreas]

Hello,

When I run this same query, I don't see where it lists the table with all of the fields, the payload only contains:

{
  "result": [
    {
      "sys_id": "7725fb04c927101091f9f06464832742",
      "name": "change_task",
      "sys_name": "change_task",
      "element": ""
    }
  ]
}

You may want to check your query and try again?

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Allen Andreas]

Hi,

Do you have a limit on the fields it returns? Within the API Explorer it's limited to 1 or 10 for testing and perhaps it just isn't getting to those fields.

Please increase your sysparm_limit to a higher number.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Gowtham Rajkuma]

Hi, 
By default this api is returning 10k records without any filters (Testing via postman). So this is not the case here. Also, the fields are missing from sys_dictionary table when I check them from Portal as well.

[Allen Andreas]

Hi,

In my post above, I said field limit, not record limit.

Anyways, if you went to your actual instance, to your sys_dictionary table and filtered like what you're using, you would have seen that even there those fields don't show up.

If you navigate to the sys_dictionary table and then filter for table = change_task, you'll see the list of fields that you'd get back. So this is what you're going to see based on what you are querying. "table" above, is the "name" field.

You'd need to include the table that change_task is extended from as well such as:

name=change_task^ORname=task

in your sysparm_query.

Please mark reply as Helpful/Correct, if applicable. Thanks!