Catalog Checkout widget -Requested for field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2020 12:50 PM
when you order an item from the portal, SC Catalog Item widget calls Catalog Checkout widget(id= sc-checkout)
I want to change data that Populates for the field Requested for
I want data in that field to be from specific variable on the item.
where on Catalog Checkout widget can I modify the code?
- Labels:
-
Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2020 03:40 PM
Hi Joyce,
'Request For' field is the 'sn_record_picker' control. You can refer below link for more details.
Reference Fields with the snRecordPicker Directive
The control is displaying data from 'sys_user' table (display field: name & value field: sys_id). You need to remove these settings and assign the required value from the variable which is available in UI using client script.
If you have a list variable then you can use ng-repeat to display those values.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2020 06:14 AM
Thanks Soumalyo.
I do not know how to accomplish your suggestions. I am new to scripting.
I am also wondering why I need to use client script while the error is on Portal view. RITM table responds correctly even if portal displays the wrong name.
I do know that my solution lies in these lines of code on server script of Catalog Checkout widget
Do you know how I can fix it.?
This is New York version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2023 04:41 AM
I have the same question as well. Not sure how we can implement this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2024 07:16 AM
Dear Joyce,
I am aware some time has passed ever since you asked your question. However, I stumbled upon it, and, after a day of painful code crawling in finding an answer to that exact same question, please let me enlighten you with my findings:
The answer lies in the data object, which is one of the global data sources to find in this scope. If the script debugger has a good day, it will give you a revealing insight.
As you can see, you can use
data.item.fields
to get to the honeypot. I hope this helps you or somebody else on their journey.