Skip to main content
  • EN

Hello everyone,

 

I am trying to use a SQLExecutor with embedded connection parameters provided by some published user parameters. Here's an exemple:

imageAfter saving the SQLExecutor parameters and reopening it, it seems that the last parameter (password param, i.e DB_PASSWORD) is not being persisted:

imageAt first i thought that it would not affect the connection parameters (i.e. maybe an small UI bug), but that's not the case since the SQLExecutor did not use the provided $(DB_PASSWORD):

image This is a local test, but i have similar results when targeting prod servers.

Interestingly, this happens on FME2022.2 (Build 22765) but not on FME2018.0 (Build 18312)

 

Do you notice the same behavior on your workbenchs ? Is there's an workaround for that? (I tried using an ParameterFetcher, same results)

Thanks in advance!

 

 

I'm currently working on a workspace that connects to a postgres DB with embedded connections set via user parameters as per your example and haven't encountered this issue. The password remains. That is in FME 2021.0.0.0

I've tried reproducing the issue in FME 2022.2 (Build 22765) but haven't had any success. When I open and close the SQLExecutor it preserves the password.

 

Did you perhaps open up an old workbench from FME 2018.0 in FME 2022.2? Does the SQLExecutor transformer need updating at all? If it does try updating the transformer to see if that resolves the issue. If you did open an older workspace in FME 2022.2, try creating this part of your workflow from scratch and see if the issue still exists.

 

Let me know how that goes.

Thanks!

I can reproduce in 22795 - New fresh workspace - If I define the parameters in the workspace first and then assign them to SQLExcecutor and reopen the password is gone.

 

Indeed if I try to run it after reopening and the password is gone then I will get the same error as you. If I don't reopen the settings then the process will run (at least it does for me).

 

I also just tried putting in the password with text and it was gone so not related to published parameters.

 

Looking at the saved workspace in text editor you can see that the value is defined correctly.

 

image 

I did eventually get it into a state where the settings would persist which was strange. I couldn't tell you when the witch happened or what I did.

 

Thanks for the answers!

@danminneyatsafe (Safer)​ At first I opened the FME 2018.0 workbench on FME2022.2 and proceeded to upgrade all the transformers, that's when i first noticed this problem. I also observed the same problem when copying-pasting the FME2018 transformer in a blank FME2022 workbench. At last, i could reproduce the same bug on a empty FME 2022.2 workbench and manually setting the user parameters. There's a minimal reproduction example attached (It affects both SQLCreator and SQLExecutor).

@virtualcitymatt​ That's exactly the behavior observed here! It's possible to run the SQLExecutor after setting the password, but any other updates in the executor (such an update in the SQL statement, a modification on the exposed attributes or even a simple open transformer params -> OK causes the bug to appear). It's indeed not a problem with the published parameters (bug persisted when using a type text on the parameter or using a attribute from ParameterFetcher, even after successfully logging these values), it is indeed something related to the password field in the SQLExecutor parameters.

Furthermore, the "solution" of not opening the SQLExecutor parameters after setting the password does not work when uploading the workbench to a FME Server

Thanks for the answers!

@danminneyatsafe (Safer)​ At first I opened the FME 2018.0 workbench on FME2022.2 and proceeded to upgrade all the transformers, that's when i first noticed this problem. I also observed the same problem when copying-pasting the FME2018 transformer in a blank FME2022 workbench. At last, i could reproduce the same bug on a empty FME 2022.2 workbench and manually setting the user parameters. There's a minimal reproduction example attached (It affects both SQLCreator and SQLExecutor).

@virtualcitymatt​ That's exactly the behavior observed here! It's possible to run the SQLExecutor after setting the password, but any other updates in the executor (such an update in the SQL statement, a modification on the exposed attributes or even a simple open transformer params -> OK causes the bug to appear). It's indeed not a problem with the published parameters (bug persisted when using a type text on the parameter or using a attribute from ParameterFetcher, even after successfully logging these values), it is indeed something related to the password field in the SQLExecutor parameters.

Furthermore, the "solution" of not opening the SQLExecutor parameters after setting the password does not work when uploading the workbench to a FME Server

Hmm, my test will run on FME Server just fine if I don't mess with the parameters after uploading

Hmm, my test will run on FME Server just fine if I don't mess with the parameters after uploading

After tinkering a bit the wb (recreating params / transformers, editing the wb with text editor, etc) it seems that the password is now persistent (even after upload to FME Server). Thanks!

Hmm, my test will run on FME Server just fine if I don't mess with the parameters after uploading

We've found today that the password parameter had been wiped, we uploaded to one FME Server instance and it persisted and ran ok, then downloaded from FME Server and it was blank again. So I spoke too soon up thread!

@eliton​ Retesting your workspace I was able to reproduce the issue. Oddly enough I can't create the issue myself from a brand new workspace, but I can reproduce it with your provided workspace.

 

In FME 2023.0 I found that the Password parameter would only reset if I set the password parameter to the user parameter, saved the workspace, closed the workspace, and then re-opened the workspace. The parameter would not reset itself unless I closed and opened the workspace. In FME 2022.2 however the password parameter would reset every time I opened and closed the transformer.

 

I've filed a ticket (FMEDESKTOP-14222) to get this issue resolved. If anyone else comes across issues related to this, or other steps used to reproduce the issue, let me know and I'll add them to the ticket.

 

Thanks!

​Hi @eliton​, I'm pleased to share that the issue @danminneyatsaf​ filed (FMEDESKTOP-14222) has been resolved by our development team and the fix is available in FME 2022.2 build 22800 and newer. You can find the fixed build available here in our Downloads page for FME 2022.2 Official: https://engage.safe.com/support/downloads/#official

​Hi @eliton​, I'm pleased to share that the issue @danminneyatsaf​ filed (FMEDESKTOP-14222) has been resolved by our development team and the fix is available in FME 2022.2 build 22800 and newer. You can find the fixed build available here in our Downloads page for FME 2022.2 Official: https://engage.safe.com/support/downloads/#official

Awesome, thanks for the quick fix.

​Hi @eliton​, I'm pleased to share that the issue @danminneyatsaf​ filed (FMEDESKTOP-14222) has been resolved by our development team and the fix is available in FME 2022.2 build 22800 and newer. You can find the fixed build available here in our Downloads page for FME 2022.2 Official: https://engage.safe.com/support/downloads/#official

Great news! Thanks for the assistance and the quick fix

Reply


Community Stats

30,120
Posts
114,321
Replies
37,748
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.