Unanswered

Azure SQL modified trigger - table names not visible

(1) Share

Report

Posted on by Community Power Pla...

Hi everyone,

I've got an Azure SQL database and I want new or modified records to trigger an approval email using Flow. I've successfully done this for new items using the "When an item is created" trigger, where I can select the table I'm interested in from the "Table names" drop down, see below.

Problem is, when I use the "When an item is modified" trigger using the same connection as before, I do not get a list of available tables in the drop down, and I have to enter the table name manually.

This does not run but instead I get a series of "failed checks" - bad request. Details below.

{
  "status": 400,
  "message": "Invalid Mashup Expression using supplied values.\r\n     inner exception: The key didn't match any rows in the table.\r\nclientRequestId: e1172451-d371-43b7-bbbb-620d55a8f059",
  "source": "sqlconnectionprovider-northeurope.db3-ase-001.p.azurewebsites.net"
}

Anyone have any ideas? Is the error linked to my inability to select the correct table?

Thanks, Adam.

Categories:

Building flows

I have the same question (0)

All responses (14)

Answers (0)

v-monli-msft on at

Like (0)

Report

Hi @Anonymous,

Like your guess, I think this issue is related to that there is no tables shown in the dropdown list when you creating the flow. If might be that your connection to Azure SQL is corrupted. Please try to re-add the connection with add new connection feature when you create the flow.

Regards,

Mona

Was this reply helpful? Yes No
Community Power Pla... on at

Like (3)

Report

Hi @v-monli-msft, I've created a new connection to the database and the same issue occurs; the list of tables is available in the create trigger but not in the modified trigger.

Was this reply helpful? Yes No
jehrenfeld 43 on at

Like (3)

Report

I am having the same issue. Did you ever get the issue resolved?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

No I didn't. If I do end up using Flow then I may have to design my solution around the create trigger only. The main reason for using Flow was to allow me to send actionable messages - if this can't be resolved I may have to look into writing my own.

Was this reply helpful? Yes No
jehrenfeld 43 on at

Like (2)

Report
I just came across this. I am using a gateway to connect to my database, but some table show up but a whole bunch do not.
https://flow.microsoft.com/en-us/blog/introducing-triggers-in-the-sql-connector/ Near the bottom of the page:
Limitations
The triggers do have the following limitations:
It does not work for on-premises SQL Server
Table must have an IDENTITY column for the new row trigger
Table must have a ROWVERSION (a.k.a. TIMESTAMP) column for the modified row trigger

Was this reply helpful? Yes No
jehrenfeld 43 on at

Like (2)

Report

I found the issue. Your table must a column with a timestamp datatype. I added a column called tRowVersion and set the datatype to timestamp and now it shows up in my dropdowlist of table.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Thanks @jehrenfeld, I will give this a try and report back.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

I tried the turnaround to SQL Server connector limitation for UPDATES

The IDENTITY columns iD int ALSO MUST BE THE PRIMARY KEY or the connector tries to update the row with the primary key field = the ID Number..... (That is NOT yet written in the SQL Server limitations page)

You also need a ROWVERSION timestamp but it is not used in the generated sql for updates.

I did not try the On premise but I will definitly need it in the real world.

If you do not see the tables, just type the Table name, sometimes the list comes, sometime not but it works.
Best regards

Was this reply helpful? Yes No
jehrenfeld 43 on at

Like (1)

Report

I tried all of that and I still get an exception error when I try to connect to that table. Very frustrating as the Created trigger is working nicely, however, the workflow is useless without the ability to trigger a step when the status changes in my table.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

So you confirm that it still does not work with on premise sql server, what is the error message, do you have, what is the SQL server version (some utilities does not work with 2017)

Was this reply helpful? Yes No