Azure SQL modified trigger - table names not visible

[Anonymous]

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.

[v-monli-msft]

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

[Anonymous]

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.

[jehrenfeld]

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

[Anonymous]

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.

[jehrenfeld]

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

[jehrenfeld]

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.

[Anonymous]

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

[Anonymous]

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

[jehrenfeld]

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.

[Anonymous]

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) 

[jehrenfeld]

SQL Server 2012

[Anonymous]

Why powerBI comes into this ??? DId you try to type the table name ?

[jehrenfeld]

I did try typing the name but then I do not get any dynamic fields to use in Step 2. This is not for PowerBI. This is a workflow to send a text message to a user when the status in the table changes.

[Anonymous]

They may have uses PowerBI Gateway for Powerapps.... Any way triggers for update are not yet supported for on premise sql server, this may be the cause. To be sure try with Azure Cloud SQL server, you get one month free. I have no idea to help more.

If you are desperate you could create a SQL Server "on update" trigger on your table within the SQL Server Database that would create a copy of the updated record table into another temporary table and then use a "flow" on create looking at this temporary table ... May be :))