Create a "Multi Row" field on Change Request form

[Hiago]

Hi everyone! Hope y'all are doing well.

So, I have a requirement on the Change Request form, where I should create a relationship between CI's and some string values, such as "QA State", "Production Path", "Version" and more..

The first thing that came to my mind is: "Create a custom table and create the fields that you need. Then, create a related list on the Change Request form, so the user will be able to create this relationships there." But I have some limitations here to create a table (we are almost reaching the custom tables limit on this instance).

Then, a new idea came up: In the Service Portal, we have that Multi Row variable set, which by itself meets all my requirements (a "table" with all inputs required).

So the question is alive: Is there any possibility to create a "Multi Row Field" on the platform's side forms (such as Change Request form)?

If yes, how can I do that? I'm not even a coder, so if you can detail (if possible) how to implement this, i'll be grateful.

And, @ServiceNow, please, consider this type of fields on the platform side by default. It really helps for multiple scenarios.

Thank you!

[Maik Skoddow]

Hi

A MRVS is a special type for catalog variables but not available for common forms.

But you could create a record producer with such a catalog variable. For creating new changes your users then would use that record producer.

Maik

[Hiago]

Thanks, Maik.

I'm considering this alternative in case of i'm not able to create something similar on the platform side.

[Mohith Devatte]

hello @Hiago ,

it's only available as a variable set but not as the field type on any of the forms in service now .

As you might have known MVRS gives the output in array of JSON format you can do one thing as a work around there is a field type called Name value pair where it can store multiple values for different key values just like JSON.

Refer below 

Output:

HOPE THIS HELPS AS A WORK AROUND

PLEASE MARK MY ANSWER CORRECT IF IT HELPS YOU

[Hiago]

Hi @Mohith Devatte.

Thanks for your suggestion. This field looks very helpful for my requirements, but i'm facing the limitation that there's only 2 fields to be populated: Name and Value.

Is there a way to define more fields for each input (i.e. Name, Value, Date, Location)? If yes, there's also a way to define some of this fields as a reference or choice field?

That's exactly my scope:

Configuration Item; QA State; Path; Type of Object;

So, my inputs should look like:

• System A, Tested; C:\Windows...; Report;
• System B, Rejected; C:\Windows...; Table;

Thanks!