"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.

[Hitoshi Ozawa]

Hi Gowtham,

Field "additional_assignee_list" is in the "task" table and not in the "change_task" table.

So following url will return the additional_assignee_list

https://<instance name>.service-now.com/api/now/table/sys_dictionary?sysparm_query=name=task&sysparm_fields=sys_name,name,sys_id,element

[Hitoshi Ozawa]

Likewise, sys_tags is defined in a "label" table.

Some fields lie tags and worknotes are in different tables. tags are in label table and worknotes are in sys_journal_field table.

[Gowtham Rajkuma]

Please check my response on your first comment. Also, if this is the case, then we are we receiving these fields when we fetch the schema of the other table. Why are we getting `additional_assignee_list` column while listing schema of `change_task` table if it doesn't belong to it ? Same with `sys_tag` column in `text_search` table (Attaching screenshot of this case as well).

[Gowtham Rajkuma]

Hi,

I can see the field 'additional_assignee_list' in the schema of 'change_task' table's (Please see the attached screenshot). Can see this column in "change_task" table's schema from portal as well. but it's missing in "sys_dictionary" table against "change_task" table.

Same is the case with "sys_tags" column in "text_search" table, it's there in the schema but missing from sys_dictionary against this table.

Thanks.

[Abhay Kumar1]

Hi Gowtham, i have come across two scenario here when i had similar issue Either field name searching wrongly on dict or field itself does not belongs to that table. You can check about field detail if this is visual on form, by right click and show field option, there you will info about field otherwise check on form layout by selectin appropriate view you will get some idea on that. Hope this will help you.