Any solution to store multiple correlation IDs without creating custom fields?

[Suggy]

We are using  correlation ID on Incident form for an integration 'A'.

Now that we have new use cases to integrate incident with other systems 'B' and 'C' and store the respective correlation IDs we as well, is there any solution to store the IDs without creating custom fields?

[Sandeep Rajput]

@Suggy Instead of creating multiple fields, you can create one single Name Value pair field and store source as Name and value as the correlation id. 

For more information please refer to https://www.servicenow.com/docs/bundle/yokohama-platform-administration/page/administer/field-admini...

Hope this helps.

[Suggy]

@Sandeep Rajput We thought so but also felt like it would make things complex when writing and reading values from that field.

Say current value is "Intune:123"

Later and integrated with anther system it should be "Intune:123 , SCCM:456" etc

And when making updates on INC form based on correlation ID, we need to parse it properly.

[Sandeep Rajput]

@Suggy I agree the complexity will be there writing the logic to parse and update it properly will be a one time effort, and this will save you a lot fields on your table. On top of this, your solution will be scalable as you can add as many sources as you want without adding additional columns. 

[Dr Atul G- LNG]

Hi @Suggy 

I think No, you need to create the new field and better create a list collector type.