- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2025 06:19 AM
actually i m facing that error message '
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2025 07:02 AM
that should be fine, you need not worry on that info message.
that's the only way which ServiceNow allows to access outside variable within MRVS.
You can use that safely.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2025 06:44 AM
@GhitaB ,
You can follow the below approach as well:
Create a hidden variable inside the MRVS — call it copy_of_outer_variable.
Use a Catalog Client Script (onLoad) on the main catalog item (outside MRVS):
Loop over the MRVS entries and set the hidden field to the outer variable's value.
// This runs outside MRVS
function onLoad() {
var outerVal = g_form.getValue('outer_variable');
var mrvs = g_form.getValue('multi_row_variable_set');
// You can't directly set MRVS values, so use GlideAjax or inject during row creation
}
In the MRVS client script, reference copy_of_outer_variable instead of g_service_catalog.parent.getValue().
This keeps all data within the MRVS scope and avoids the unsupported parent reference.
Regards,
Mohammad Danish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2025 06:45 AM
i've tried doing this but sadly didn t work