Confiforms IFTTT "Copy ConfiForms Data" action - using entryId=[entry.id]

[Alexander Junkermann]

We have a collection of applicable best practices which is stored in form A. We need multiple instances (per project) which shall store references to this central collection in a form B. For multiple phases in a project we have separate pages in which we can trigger the copy of all best practices (from A) matching the phase (defined by the page) to form B.

A best practice can be associated to more than one phase. If we use the "Copy ConfiForms Data" action this could lead to duplicate entries of best practices in form B. 

I discovered that I can use the entryId=[entry.id] in the "Copy ConfiForms Data" action also, but this will lead to multiple identical entryIDs within one instance of confluence. They still are unique within one form, but not within the instance of confluence. 

Could the existence of multiple form entries with identical guids lead to a problem within confiforms or is it safe to go this way?

[Peter_DevSamurai · Accepted solution]

Hi @Alexander Junkermann ,

The "Copy ConfiForms Data" action in IFTTT allows setting entryId=[entry.id] to preserve the source record's ID in the destination form. However, ConfiForms entry IDs (UUIDs) are unique only within each form's dataset, not globally across the Confluence instance.

Since each form operates as an independent dataset, having identical entry IDs in different forms won't cause conflicts or problems in ConfiForms. The system scopes IDs per form, so operations like queries, updates, or references remain isolated and won't overlap -> This approach is safe for your case, as long as you handle any potential data duplicates with filters or validation rules in the destination. 

If you're concerned about broader instance and wide issues (ex: indexing or performance), it's very unlikely as ConfiForms is designed with form-level isolation. 

I hope the links below are helpful for you:

- Confiforms IFTTT rules

- Entry ID handling

Best,

Peter

[Alexander Junkermann]

Hi Peter,

thank you so much for your quick response :-)

That's what I was hoping for.

Kind regards

Alex

[Peter_DevSamurai]

Thank you so much!

Have a great weekend ahead!

[Alex Medved _ConfiForms_]

Hi @Alexander Junkermann 

Why not to create a smart field in a target referencing the form that your are copying form (source) and set it with an "[entry.id]" of the source form, to create a true link between the copied data and the original data

Alex

[Alexander Junkermann]

Actually the process creates a snapshot for a certain point in time which is built up phase by phase. If a project enters phase 1 they snapshot (some data) of all best practices for this phase. If in the meantime some data in the central database changes, the data in the snapshot shall stay the same (until actively triggered to be updated). 

But nevertheless - thank you for your idea!

Alex