I have a sharepoint list that triggers on new item creation, which creates a new row in a sql table, and then sends back the id.....
There are some items that i want to add to the sp list that are already in the sql table, which i obviously dont' want created again in the sql table. how long do i have to wait to turn the flow back on....and will the trigger be "dead"?
Or if you know a row is in SQL already, you can add a column to SP list like "InSQL" and manually check it off if you know it's in SQL, and update it from Flow when you get the SQL Row ID back. Then check if the column is checked in Flow before adding to SQL.
I think a longer term solution would be to check if the SP item exists in the SQL table before adding. And If the SP item has a SQL row id, then it shouldn't be added
Something along the lines of:
New SP Item trigger
Condition: SPItemSQLID = '
IF YES (SPItemSQLID='')
Get Rows from SQL
ODATA Filter: SQLColumnName eq SomeValueFromTrigger
Condition: empty(body('Get_rows')?['value'])
IF YES (empty rows)
Add SQL Row
IF NO (empty rows)
Do Nothing
IF NO (SPItemSQLID='')
Do Nothing
Hi rormiston,
I think you need to delete the old flow and create a new one to avoid this issue.
Regards,
Mona
Hi rormiston,
I'm not sure if I understand your question clearly. I think as soon as you have added all these items to sp list that has already exist in sql, then you can turn the flow back on... Not sure what you mean by "how long", please help to explain more.
Regards,
Mona