Regarding Hiding of the fields within the MRVS on the Portal end.

VenkataAviM
Tera Contributor

Tuesday

Hi All,

 

Description -  On portal level users should not see the Total Purchase Price value.

Also, In the MRV section, the following fields should be hidden. The below are the Field names:

Total Purchase Price of Product

Unit Purchase Price of Product (EUR)

 

Fields that are present in the Single Row Variable Set we are able to hide and we had achieved in our Instance.

 

  1. Total Purchase Price field is present in a Single Row Variable Set for our Catalog Item. After unchecking the Visible on Summaries tab for the Total Purchase Price field, we are able to hide the particular field on the Portal end. PFB the snapshots for reference.

VenkataAviM_0-1768317648493.png

Before: All the Check boxes are checked. Hence the Total Purchase Price field is shown to the User on Portal end. PFB the snapshots.

 

VenkataAviM_1-1768317648495.png

 

VenkataAviM_2-1768317648498.png

 

After: Unchecked the Visible on Summaries checkbox so as to hide the Total Purchase Price field to the end user on Portal level. Hence the Total Purchase Price field is not shown to the User on Portal end. PFB the snapshots.

 

VenkataAviM_3-1768317648500.png

 

 

VenkataAviM_4-1768317648504.png

 

Fields that are present in the Multi Row Variable Sets (MRVS) we are not able to hide and we are not able to achieve in our instance.

 

  1. We had tried the similar approach for the Purchase Field Unit Purchase Price of Product (EUR) that are present in the Multi Row Variable Sets (MRVS). After unchecking the Visible on Summaries tab for the Purchase field, we are not able to hide the particular field on the Portal end. PFB the snapshots for reference.

VenkataAviM_6-1768317648518.png

Before: All the Check boxes are checked for the Unit Purchase Price of Product (EUR) fields. Hence the particular field is shown to the User on Portal end. PFB the snapshots.

 

VenkataAviM_8-1768317648526.png

 

 

VenkataAviM_9-1768317648530.png

 

After: Unchecked the Visible on Summaries checkbox so as to hide the field to the end user on Portal level. But the field is still present on Portal end. PFB the snapshots.

VenkataAviM_9-1768317648530.png

 

 We are able to hide fields within Single Row Variable Sets. However, the same functionality does not appear to be available for fields within Multi Row Variable Sets (MRVS). Could anyone please suggest a possible approach or best practice to implement field hiding within MRVS?

 

Thanks,

Venkata Avinash.

0 Helpfuls
  • 117 Views
1 REPLY 1

Matthew_13
Mega Sage

Tuesday - last edited Tuesday

From what you’re showing, this is by design.

In Service Portal / Catalog, MRVS (Multi-Row Variable Set) is rendered differently than normal variables or single row variable sets so the same “hide/show” techniques that work for regular variables often dont apply cleanly to MRVS columns/fields.

Why you cant hide it the same way

  • For normal variables, UI Policies / Catalog Client Scripts can usually hide the field (g_form.setDisplay() / UI Policy actions).

  • For MRVS, the “fields” you see are actually columns inside a grid widget, not standalone variables on the form. Because of that, there’s no reliable OOTB way to hide individual MRVS columns/inputs just like a standard variable.

What you can do

I see you basically have 3 options:

  1. Hide the entire MRVS container (OOTB-friendly)

    If your goal is to hide the whole MRVS section, you can usually do that via a Catalog UI Policy or Catalog Client Script targeting the MRVS variable itself (not individual columns).

  2. Customize the Service Portal widget (if you must hide specific MRVS fields/columns)

    If the requirement is “hide just these MRVS columns/labels,” then you’re in widget customization territory (the MRVS widget/template). This works, but it’s customization and needs testing/maintenance.

  3. Redesign the input model (recommended if you need strict conditional visibility)

    If the business requirement is “hide/show specific fields based on conditions,” the most supportable design is to avoid MRVS for those fields and instead use:

  • normal variables with UI Policy logic, or

  • separate catalog items / sections, or

  • a different data capture pattern.

Bottom line

  • Individual MRVS column hiding isn’t supported OOTB the same way as regular variables.

  • You can either hide the whole MRVS, customize the portal widget, or redesign the form if you need conditional field visibility.

@VenkataAviM - Please mark Accepted Solution and Thumbs Up if you found Helpful!

0 Helpfuls