Is there any way to create new records in cross reference table through rest API?
The idea is to send request through rest API. This request should be added as new record in cross reference table.
Is there any possibility to do so?
You can update the cross reference tables that are exposed as extensions using the following API: EnvironmentExtensions object
However this is the configuration for the atom itself. The component in Process Library can be updated using importation by CSV.
Hope this helps!**If the post solves your problem, mark it as "Correct Answer".**You can say "Thank you" by clicking the "star" in the post that helped you.
Thank you for your quick response.
I actually called the "update" operation on "EnvironmentExtensions" object and got the updated value in the update response. But, found that the environment extensions which I set before got deleted and the updated value is not set in the cross reference table.
Can you explain the reason for this?
The EnvironmentExtensions API requires ALL values (CRT, connections, properties, etc.) to be provided in the update call. See Allow partial updates to Environment Extension via API.
Any hints ? Adam Arrowsmith Srinivas Chandrakanth Vangari Leif Jacobsen Srinivas Jilla
Actually I have been looking at your question several times since you posted it. I even started answering your question, but didn't because it wouldn't be the answer but more like a provokative debate. But now you ask for my response, I'll tell you about a different approach.
Until a year ago I was using Cross Reference Tables (CRT) in several of my integrations. I thought it was an almost perfect way to have as a lookup table. I gave the relevant users access to maintain the tables, because I didn't want to spend time doing that. Soon they asked me to extract the data. I created a process which I have shared with the community. But still it gave me plenty of headaches. My users made duplicate records, wrong / corrupt data was entered, other kinds of mistakes. One user even removed the checkmark in "Override table". All this left me with 2 choices. Either I would have to maintain the CRT's myself or I'd have to find another solution. I chose to find another solution.
The solution was to start using Google Sheets. (No, I'm not joking)
Occasionally I check the sheet, last time in august just to find my users had added some columns for additional comments, and one redundant row. Should my users create some strange error, then I will be able to change the process and protect it against that kind of error.
I have used this solution in processes where records often needs to be inserted, updated or deleted.
Now I only use CRT's in processes where it is extremely rare they need to be changed.
This has been my approach and my way of getting rid of the CRT's
Best regards, Leif
Retrieving data ...