If you have the data in a list you in the MF then you can add a loop with the list as input parameter.
Before the loop create a list that holds the persitent objects that you will be creating in the loop. (this list is initially empty)
In the loop do a retrieve from the database of the persistent entity that has the same ID as the iterator object (and maybe other contraints). After this add an exclusive split checking if the persitent entity was retrieved (something like: $retrievedObjectedFromDB = empty) then if the obejct was not retrieved (on the true exit of the split) add a create object activity and create you new persitent object. With a change list action add the new object to the list created before the loop. On the false exit add a continue event.
After the loop add a commit object(s) action and pass the list to the action to write the data to the database.
Be aware that this descrioption of the microflow does not take into account that in the initial list of emails in the MF could contain duplicates. If this is the case then first create a new empty list, add a loop with the original list and then first check if the new list contains the iterator object, if not add the object else continu to the next object. Now you have a list of unique objects and you can use this in the way described above.
Hope this helps you in finding the solution
HI – would this solution work if the records are being imported through the Excel Importer widget or the Flat File Importer widget from the app store? It would seem I’d have to have the microflow execute AFTER the import is done and not as part of the import itself?
With the Excel importer there is no requirement to use non persistent entities.
So basically you can create a persistent datamodel and link them to corresponding excel importer template.
I’m trying to put in a control where, if the user imports a file twice, the entity won’t create duplicate records … Can a “unique constraint” be set on a set of columns in an entity?