cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
GeorgiGeorgiev
Helper II
Helper II

Same connection and user setup returns ERROR on PROD environment

Hello, I have a Solution that has 2 Flows. 1 checks a record in Oracle DB, while the other does UPDATE after the check.

 

The problem is we have a 100% working Solution when using same user with same privileges on TEST environment. But, once I change the gateway, connection, connection reference and then replace the connection in the flows I get failed UPDATE. The check flow works fine. But the UPDATE flow does not. It just fails to do the UPDATE action without any error message.

 

Do you have any idea what might be causing this behaviour? The setup is exactly the same as on the Test Oracle DB, but not on the Production DB.

1 ACCEPTED SOLUTION

Accepted Solutions
GeorgiGeorgiev
Helper II
Helper II

Solution:

The solution was a bit mixed up. The reason I could not get the Production flow working was because Oracle connector requires and works with Row ID column identifier. For TEST environment the views that I used were constrained for the columns I use as Primary Keys (fakturanr and belegnummer). So the TEST environment was working.

 

When switching to Production env. I tried working with base tables, not views. But, base tables did not have the same PK constraint on the same fields (PK columns are ID and IDFAKTURA). So the workaround was to use GET ROWS action in Oracle connector to match a specific row and return only the PK column, which after that was SET in a flow variable. Details on the setup now can be found in this thread:

 

https://powerusers.microsoft.com/t5/Building-Flows/Oracle-SELECT-PK-based-on-variable-input/m-p/1734...

GeorgiGeorgiev_0-1661513640211.png

 

View solution in original post

4 REPLIES 4
GeorgiGeorgiev
Helper II
Helper II

I think I finally figured out why. Since we are using VIEWs we have not set a constraint so that the view can have a PK. And Flow requires a constraint PK for the view to be allowed to make a change.

Hi @GeorgiGeorgiev ,

 

Nice work! Please accept your reply as solution and help other users easily find it.

 

Best regards,

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

Hi @v-jefferni , I am still working on a workaround as things are more complicated, but once I do make the final setup I will post an answer and accept it as solution.

GeorgiGeorgiev
Helper II
Helper II

Solution:

The solution was a bit mixed up. The reason I could not get the Production flow working was because Oracle connector requires and works with Row ID column identifier. For TEST environment the views that I used were constrained for the columns I use as Primary Keys (fakturanr and belegnummer). So the TEST environment was working.

 

When switching to Production env. I tried working with base tables, not views. But, base tables did not have the same PK constraint on the same fields (PK columns are ID and IDFAKTURA). So the workaround was to use GET ROWS action in Oracle connector to match a specific row and return only the PK column, which after that was SET in a flow variable. Details on the setup now can be found in this thread:

 

https://powerusers.microsoft.com/t5/Building-Flows/Oracle-SELECT-PK-based-on-variable-input/m-p/1734...

GeorgiGeorgiev_0-1661513640211.png

 

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (3,283)