- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2017 06:47 PM
I am not able to figure out why the Approving (document_id) field will not display on our Approval form so am seeking some suggestions.
Here is the form not showing the Approving field:
I do have it added to the form as seen below:
I am looking in the Default view:
I am able to see the field and value in the list view:
I have checked ACLs and there are none showing as a deny, which is also backed up by the field showing up in list view.
I disabled all client scripts and UI Policies on the form. - UPDATE: No I didn't disable all UI Policies, see the answer.
Chrome dev tools at least has the element showing with a value. When I hover my mouse over the element, nothing is highlighted on the form like what happens for other fields like "Approval for".
Does anyone have any suggestions on what else to check?
Solved! Go to Solution.
- Labels:
-
User Interface (UI)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2017 07:21 AM
Deactivate ui policy and check
Ui Policy:
"Check for presence of new document_id field. If it is not on form, display the legacy sysapproval form."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2017 09:19 PM
Can you please just try adding source table as well to the form layout and check?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2017 06:48 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2017 07:21 AM
Deactivate ui policy and check
Ui Policy:
"Check for presence of new document_id field. If it is not on form, display the legacy sysapproval form."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2017 07:31 AM
I am an idiot. I missed a UI Policy. We did have the one you mentioned disabled but we had another one called "Hide / Lock down field always". I swear I disabled it when testing but when I looked back at it again it was enabled. Maybe if I had taken the time to read the name or actually open it then I wouldn't have had to have made this post in the first place.
Thanks for you help!