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?

[Veer]

@Suggy 

Try to store the correlation values in the JSON format with key as third party system names and value as unique values. and while retrieving try retrieving  the required value by dot walking.

Please mark this as helpful / accepted solution if it resolves your query.

Thanks & Regards

Veer

[Suggy]

Let me try that keep you posted

[Viraj Hudlikar]

Hello @Suggy 

Without custom fields there is way, but it depends how you are going to utlize it further as its mostly reporting purpose from client side.

-> Use a single field to store multiple correlation IDs by concatenating them with a delimiter (e.g., commas or semicolons). This way, you can store all IDs in one field and parse them as needed.
->Store the correlation IDs in a single field using JSON format. This allows you to store multiple IDs in a structured way and easily parse them when needed.

->If there are any existing fields that are not being used, you can repurpose them to store the correlation IDs for the new integrations.

->You can create a related list to store correlation IDs in a separate table that references the incident record. This approach allows you to maintain a clean structure and avoid cluttering the incident form with multiple fields.

If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.

Thanks & Regards
Viraj Hudlikar.

[Ankur Bawiskar]

@Suggy 

you can use name-value pairs field type and store the data like this.

you can manipulate the JSON as well

Name-value pairs field type 

better explanation here

Exploring dictionary types : Name-Value Pairs 

If my response helped please mark it correct and close the thread so that it benefits future readers.