Reference field values are not visible in Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2022 09:46 PM
I have an HR Service (Scope - Human Resources: Core) in the ESC Portal.
I have created a custom table "Routing ID" in Global scope which extends CMDB CI Table.
I have a variable in the HR Service which is referenced to the custom table. I have records in the custom table but still I am unable to see any records from the Portal. It says "no matching records found"
I have given the custom table Read ACL to my user, and also given the cmdb_read role to my user, still the same issue.
Please let me know what I can check to get this fixed.
Thank you.
- Labels:
-
Employee Service Center
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 01:07 AM
Yes, I have set the Display to True for one field:
Still no difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 01:12 AM
Is there any specific requirement for inheriting table from Configuration Item Table? Also have you done any configuration to CMDB CI table ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 01:38 AM
No configurations are done on the table. It's just that we need a table to store the IDs. We have a limitation of creating a table in HR Scope therefore created the custom table in Global and extending the Configuration Item table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 01:42 AM
Interestingly,
I updated the table of the referenced variable to "Incident" and I am able to see incidents in that variable from the Portal.
It means, the issue is just with the custom table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 01:46 AM
Yes, Because configuration item table is having restrictions and hence same restrictions are being applied to your trigger table, I would like to suggest create a Stand alone table instead of extending as there is security issues and as per your requirements you just want to store ID's , no dependency for CMDB CI table.
Let me know if this works ...