Entity Filters missing Tables from drop down menu

JahanzebB
Mega Guru

I have sub-Prod instance which was recently upgraded to Orlando version. When trying to add a Table to  new Entity Type Filter, the only option shown is None. Verified that all entitlements are available in this instance. Is there a property or another setting that needs to configured to view tables? 

 

Here are some steps to reproduce the issue:

Scoping > Entity Types
Create New Entity Type
From the Entity Type> Related Lists > Entity Filters > Create New record
Select Table from drop down menu.
The only options shown in the Drop Down menu is None.
Prior to the upgrade, we could view all tables from CMDB, for example, CMDB_CI, CMDB_CI_SERVER, etc.

1 ACCEPTED SOLUTION

Phil Swann
Tera Guru
Tera Guru

It's a new issue, waiting for a PRB number to share - but you need to modify the dictionary attribute to prefix the EntitlementUtils with sn_grc.EntitlementUtils 

 

Please raise the issue with HI and explain the fix above has been applied.

 

Curiously... Please can you confirm the scope of the field 'table' ? IMO this should be under GRC: Profiles, but seems to have been changed to Global in cases where this issue occurs. 

View solution in original post

13 REPLIES 13

tsylte
Tera Contributor

I just encountered the same issue, has this been fixed? I'm not able to access the PRB record, wondering what the "ARTICLE_TEMPLATE_FIELD_SYS_ID" represents in the following line of the script:

g.addQuery('sys_id', 'IN', <ARTICLE_TEMPLATE_FIELD_SYS_ID>);

This is a serious matter, you should not try and fix yourself. There are likely other tables which have fields which have changed scope. Raise with SN Support and quote the PRB number PRB1400680. They should provide a script to run on your instance, specific to your organisation.

bryan_strasburg
Mega Guru

Same issue.  And, can't access this PRB record.

Key thing:  the same issue is occurring when using the Table Name field in a custom scoped application.

Anyone aware of how to address this?

This is a serious matter, you should not try and fix yourself. There are likely other tables which have fields which have changed scope. Raise with SN Support and quote the PRB number PRB1400680. They should provide a script to run on your instance, specific to your organisation.