SchemaProcessor does not display fields inherited from parent tables - Known Error

SchemaProcessor does not display fields inherited from parent tables Description SchemaProcessor does not display fields inherited from parent table

Steps to Reproduce

1. Create a role called "read_schema" 2. Create a user called "test_schema" and assign the following roles:

rest_service soap_query read_schema

3. Login as user test_schema and go to:

https://INSTANCE_NAME.service-now.com/api/now/table/pm_project/6430662053471010dc76ddeeff7b1294 https://INSTANCE_NAME.service-now.com/pm_project.do?SCHEMA

Without any ACLs for read on table pm_project you will get an permission error.

4. Create 2 ACLs on pm_project table, one for table read and one for fields read. Add role "read_schema" to both ACLs.

5. Go back to:

https://INSTANCE_NAME.service-now.com/api/now/table/pm_project/6430662053471010dc76ddeeff7b1294 https://INSTANCE_NAME.service-now.com/pm_project.do?SCHEMA

Notice that TableAPI on pm_project displays fields like: start_date end_date

that are inherited from planned_task (parent table)

Notice that SchemaProcessor does not display these fields.

Try also WSDL processor:

https://INSTANCE_NAME.service-now.com/pm_project.do?WSDL

and noticed these fields are displayed.

6. Create 2 more ACLs on planned_task table, one for table read and one for fields read. Add role "read_schema" to both ACLs.

7. Go back to:

https://INSTANCE_NAME.service-now.com/api/now/table/pm_project/6430662053471010dc76ddeeff7b1294 https://INSTANCE_NAME.service-now.com/pm_project.do?SCHEMA

and observe that now both Table API and SchemaProcessor display the fields start_date and end_date.

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.