Custom Table fields not showing up in Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-03-2017 07:25 AM
Hi,
I created a custom table (not extending task table). It is just like incident table, but there are some differences. Then I created a Record Producer, so that I can use it from Service Portal. All the fields are visible there. Now I submitted the form and a new record was created.
But when I try to show this in the header menu in service portal(My Requests and Incidents) , it is showing up just as a blank record. That means it is not detecting the field labels as it is doing for Incidents. I double checked. I have copied the OOTB code for Incidents and Requests and just changed the values for my table fields.
Can somebody help? Also when i click on this blank link, it takes me to the ticket details, where again, there is no values. Only the sys_updated_on field is populated.
Is there any restriction that only OOTB tables can be used?
- Labels:
-
Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-03-2017 07:40 AM
when you create new table be sure you also create the needed ACL permissions to read/write/create/delete on that table. to me this looks like an ACL issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2017 11:38 PM
Hi Nathan,
Sorry for delayed response. I checked again. But it does not seem to be ACL issue. Because in the Portal Homepage, there is a widget called My Requests and Incidents. There I manipulated a bit and I could see my new "ticket" from custom table, with Short description and auto-number, etc.
But again, when i clicked on that, it took me to the ticket details page, which was almost blank. No number, no short description, no assigned_to. And here when I wrote something on the "Type your message here" field, it indeed updated the original worknote of that ticket. So it should not be an ACL issue.
Regards,
Manas