Skip to main content
  • EN

Hi,

In workspace_01 I have a WorkspaceRunner transformer that runs workspace_02 that uses a SQLExecuter transformer.

The SQLExecuter utilizes a parameter to receive the Named Connection required (e.g., gisdata_01@SDEDB or gisdata_02@SDEDB, etc..) that's working great.

However, the issue happened within the workspace_01 with the WorkspaceRunner, unless I select from the available named connection to assign, the workspace_02 won't work successfully; i.e. assign by 'Attribute Value' or 'User Parameter' from the sub menu.

A closer look into the log window revealed how the parameter was interpreted/passed to the workspcase_02 as:

--SDE_NAMED_CONNECTION {\\<at>Value<openparen>_Named_Connection<closeparen>}

While it should be:

--SDE_NAMED_CONNECTION' `gisdata_02@<at>SDEDB' `

#FME 2016.1

Please help

Hi @sami_snunu, as you observed, it seems that the NAMED_CONNECTION parameter created from the Create User Parameter command associated to a Connection setting field doesn't decode the parameter value passed through the WorkspaceRunner.

This workaround might work for you:

  1. In the workspace_02, create another published parameter with Choice type, e.g. named DB_CONNECTION, and add the available connection names - "gisdata_01@SDEDB", "gisdata_02@SDEDB" etc. to the choices.
  2. Convert the original NAMED_CONNECTION parameter to a private parameter, and link it's default value to the DB_CONNECTION. See the screenshot below.
  3. In the workspace_01, set an attribute value to the DB_CONNECTION parameter in the WorkspaceRunner.

Many Thanks @takashi, that worked perfectly! :-)

I also appreciate your effort and time for the illustration in the screenshot.

Reply


Community Stats

30,129
Posts
114,378
Replies
37,768
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.