Restricting Child Table Records from Application Reference Lookups
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7 hours ago - last edited 6 hours ago
Hello team,
We have a requirement to use a CMDB-based table in ServiceNow because an existing integration with a third-party application is configured to retrieve data only from CMDB tables. Therefore, instead of creating a new standalone custom table, we need to use a table that extends an existing CMDB table.
To meet this requirement, we are using a child table that extends cmdb_ai_appl and are currently reusing the inherited CI Name field for our custom requirement.
However, because of ServiceNow table inheritance, records created in the child table are also returned when the parent Application table is queried. This behavior is not limited to the Application table list. Wherever the Application table is referenced, the child-table records may also appear in the reference lookup.
If a child-table record has the same CI Name as an existing Application record, users may see multiple records with the same name. This creates confusion because users may not be able to distinguish between:
- The actual Application record maintained in the parent Application table.
- The child-table record created specifically to support our custom requirement and third-party integration.
Additionally, end users do not have visibility into the Class (sys_class_name) field to differentiate these records. Therefore, when the Application table is referenced from other forms, the actual Application record and the child-table record may appear identical to the user, creating a risk of selecting the incorrect record.
We have configured the required ACLs on the child table, and the child-table records need to remain globally readable to support the integration and business requirement. Therefore, completely restricting read access to the child table is not a suitable solution.
Guidance Required
We are looking for the recommended ServiceNow design approach for this scenario:
Is there a supported way to exclude the child-table records from being returned through the parent Application table and its reference lookups, while still keeping the child table globally readable?
If restricting child records from parent-table queries is not recommended due to CMDB table inheritance, should we consider using dedicated fields on the child table instead of reusing the inherited CI Name field?
Our objective is to continue using a CMDB-extended table to support the existing third-party integration, maintain the required global read access to the child table, and at the same time prevent custom child-table records from appearing as duplicate or misleading Application records to end users.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
@Mad3 ,
Instead of Is in the condition builder use, Is Not to restrict one table that you dont want.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Well, there's an OOTB ServiceNow business rule that uses it, so it's there for a reason. I wouldn't over-use it, but it would work for this scenario. I'm not aware of another way to do what you are trying to do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
user query