web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / clear triggers, sharep...
Power Automate
Unanswered

clear triggers, sharepoint list

(0) ShareShare
ReportReport
Posted on by 4

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"?

Categories:
I have the same question (0)
  • v-monli-msft Profile Picture
    Microsoft Employee on at

    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

  • rormiston Profile Picture
    4 on at
    I added several rows to my SP list, and then turned flow back on about 10 min after. I'm on the highest tier account type, so I assume that I'm on 5 min cycles. When I turned flow back on, it added the rows to the SQL table and sent the ID's to the new rows replacing the SQL ID# I had already put in the SP table manually, so I had to manually change them back so the update flow would work when needed.

    It made me wonder if I didn't wait long enough, or if a new row trigger holds?
  • v-monli-msft Profile Picture
    Microsoft Employee on at

    Hi rormiston,

     

    I think you need to delete the old flow and create a new one to avoid this issue.

     

    Regards,

    Mona

  • michowl Profile Picture
    Microsoft Employee on at

    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

  • michowl Profile Picture
    Microsoft Employee on at

    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 286

#2
David_MA Profile Picture

David_MA 256 Super User 2026 Season 1

#3
Expiscornovus Profile Picture

Expiscornovus 225 Most Valuable Professional

Last 30 days Overall leaderboard