Flow Trigger - SQL New Item Created

[mindrift_io]

Hi there,

I am trying to set up a flow that triggers after a new row has been added in an SQL DB. I have set up and connected the SQL DB with Power Automate via a gateway and I have set up the first version of the flow. I added new rows to the SQL DB manually via MS SQL SMS, but the trigger does not react. When I test the flow it does work, but only takes the first/oldest row from the SQL DB as an output. I want the flow to only take the newly added row (which should trigger the flow) as an output for my following steps. Do I need to add a "Get row) step afterward? Why is the flow not triggering when I add new rows to the table? Why is it only taking the oldest row from the table as an output?

BR
Thomas

[abm]

Hi @mindrift_io 

Could you please post a screenshot of your flow?

Thanks

[mindrift_io]

[abm]

Hi @mindrift_io 

Thanks for the screenshot. When ever you add a new row flow should trigger. The flow runs are async. So there some time delays for the trigger. If you add three rows continuously flow should trigger three times. Not sure you meant by old  records. Is that something you added earlier? Have a look at the run history and make sure all runs are logged there. Open the history run and check all data is correct.

Thanks

[mindrift_io]

Hi @abm 

the flow has been done for 20 minutes now and nothing has been triggered. What I mean by old records is the following: 

To test if the flow triggers correctly (which it isn't) I am adding rows to the Table manually. The flow dows not trigger so I test the flow manually using SQL data option. This does work and the flow runs, but always using the first added row. For example: I added 3 rows manually:

Row 1
Row 2
Row 3

When I test the flow the second step of the flow works and adds a message to Teams, but with the "Row 1" and not with the latest "Row 3".

That's my 2 issues - The flow is not triggered by new rows in the table ... even after 20 minutes. And The output value is always the oldest row and not the newest added (which should trigger the flow).

BR
Thomas

[abm]

Hi @mindrift_io 

Thanks for your quick reply. Could you add a new connection for the trigger and try?

Thanks

[mindrift_io]

Do you mean a new connection to the existing DB or a new connection to another table?

[abm]

Hi @mindrift_io 

Existing trigger. Also when you enter manually make sure press tab to next row otherwise it won't treat as saving the record.

Thanks

[mindrift_io]

I disconnect and readded the connection to the DB and tried with the existing flow and with a new flow and nothing changed. I also added the rows with a tab and when using "Get rows" I can see all entries in the output. I would really like to know why the flow is not registering the new row and not triggering the flow as it should.

[abm]

Hi @mindrift_io 

Sometimes the flow trigger take time to do all the refresh it needed. Is this working for you now? 

Thanks

[mindrift_io · Accepted solution]

After some trial and error I found the solution myself. In case this might help somebody with the sme issue:

The issue was that I did not define a key ID in my table. After adding a key to the table Power Automate correctly registers new rows in the table. Even when bulk inserting power automate correctly triggers the flow N amounts of times where N=the amount of rows added in bulk.

[bolandre92]

Hi, 

I am having the same issue and seems that you have solved it. Could you please stress more on this "The issue was that I did not define a key ID in my table" and how did you solve it step by step?

That would be extremely helpful.

Thank you 

[mindrift_io]

Hi Bolandre,

the issues was the table that I created in SQLSMS did not have a key ID value with incrementally increasing IDs. 

https://stackoverflow.com/questions/10991894/auto-increment-primary-key-in-sql-server-management-stu...

I created an auto-incrementing ID in the table and this was obviously needed for flow to understand the structure of the incoming rows.

Hope this helps!

BR
Thomas

[calerof]

Hi @abm ,

What happens if there are no new records created in more than 90 days? I'm thinking of a dimension table that normally is not modified frequently. What would be a turn around to avoid the Flow to get disabled.

Thanks,

Fernando

[abm]

Hi @calerof 

Good question. Couple of workarounds for this but not straight forward.

1. Create another table to keep track of the last updated date. Create a new flow scheduled trigger every day to check when is the last date created. If its nearing the 90 days limit then try to run the flow with some dummy value create or update.

2. Create a custom connector. Pass the flowname and environment name. Check the run history. If its nearing the 90 days limit then try to run the flow with some dummy value create or update.

See this blog about how to get run history

How to create custom connector to get the flow run history - Power Platform/Dynamics 365 CE/DevOps B...

Thanks