journal_input fields not displaying on portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 12:46 PM
Our team created a couple journal_input fields on a form and it shows up on the back-end platform view, but does not display on the portal unless we make it mandatory. What is stopping the portal form widget from displaying these types of columns?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 01:00 PM
I have a couple initial thoughts that could cause this.
- Is there a UI Policy, or Client Script, making the field hidden on SP view? Setting it to mandatory would override that UI Policy.
- Is the record's SP view configured to show the field?
- Check your ACLs on the field to make sure there's nothing crazy going on there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 01:19 PM
hey @Chaz, we've checked UI Policies and Client Scripts and there are none that would be preventing these fields from showing. We're also trying to render this on a specific view and there are no ACL's at all on those fields. I'm wondering if there's something preventing those column types from showing up on portal globally.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2025 03:27 AM - edited 05-25-2025 03:29 AM
Hi @davilu,
Like you have mentioned your team has created jounal_field... In order for anyone to access those journal fields you need to ensure that you create read and write ACL's for those journal fields and grant them very specific roles who are "entitled" to read and write from portal view.
Reason : This is how your license metric gets calculated. If users who do not have right level of read and write access then they cannot read and write because Portal widgets are designed to check if the logged in portal user has read and write access or not. For example see "standard ticket conversation" widget configuration below.
It will hide the journal fields if portal users do not have right roles and ACL's defined for them.
Hope it helped to understand the functionality.
Bonus tips: User "Access Analyzer" and "Access Analyzer Simulator" to quickly analyze and find the right ACL's and Roles to grant access. This makes life lot easier. Cheers!
Let me know if it worked.
Regards,
Vikas K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2025 07:25 AM
Hi @VikMach , I tried your ACL method but it did not work. Just so we're on the same page, I'm trying to get a journal_input field to show on the portal form. The journal_input field below shows up in the platform UI, but will not show up on the portal form: