Unanswered

Same connection and user setup returns ERROR on PROD environment

(0) Share

Report

Posted on by GeorgiGeorgiev

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.

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (1)

GeorgiGeorgiev 93 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
v-jefferni on at

Like (0)

Report

Hi @GeorgiGeorgiev ,

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

Best regards,

Was this reply helpful? Yes No
GeorgiGeorgiev 93 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Verified answer

GeorgiGeorgiev 93 on at

Like (1)

Report

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/1734393/thread-id/191954#M192387

Was this reply helpful? Yes No