I cannot insert a row in an on premise SQL database.
I get the following error:
The gateways are upgraded to the latest version.
When I add the "insert row"-action, the database and its tables are being resolved.
There are no sql-triggers on the table. It's a simple table with just two columns.
I have an existing flow with an "insert row"-action to the same database and this one works fine, but each new flow that I create with this sql-action give me this error.
@Anonymous ,
No, i do not have the ability to do anything with the tables. They cannot be altered in any way because they are part of a purchased software system.
In fact, I am getting the same problem with actions I'm creating new from all tables and views I have tried from that same SQL instance. BUT... I am using these tables in existing flows, and they are working.
Of course, I will not be messing with those flows because I have had issues in the past that simply saving a flow during the time there was some sort of a Micorsoft issue with Flow was enough to kill the flow from subsequent execution.
Did you recreate the table on the sql-server?
Yea, that is what I normally do as well with cases similar to this. In my case, even creating the flow again from nothing yeilded the same result!!
@martinav : I'm not sure, but I think that I've deleted the table, recreated it and that the error disappeared.
Having the exact same issue. I have MANY SQL actions in other flows that are working. I am trying to create new actions in a new flow (tried creating new twice) with the same ill result!
@Anonymous , did you get a positive result?
Hi @Anonymous,
Perhaps you could consider configuring a new connection for this action and then giving the connection a new name.
Please take a try again.
Best Regards,
Hi Barry,
Authentication Type on my connection is already Windows.
As I mentioned in my post, I have another flow which inserts rows to the same database without problems, this flow uses the same connection.
Best Regards,
Sam
Hi @Anonymous,
I did a test on my side and didn't meet the issue you mentioned.
Image reference:
For reference, when I configure the connection, the Authentication Type selected is Windows.
Please use Windows authentication to configure the connection and try again and see if issue still exists.
Best Regards,
Barry