Import parameters {DataConnectorName}, {Schema}, {TableName}

alexej · October 26, 2017, 8:01am

Is it possible to read “import-transformation” parameters such as {@DataConnectorName}, {@Schema}, {@TableName} in order to use them as the metadata (f.e.: data-lineage)?

dgudkov · October 26, 2017, 2:13pm

Hi @alexej,

A .morph file is just an XML file. You can extract from it the connector name and the table name (including schema) using standard means for parsing XML files – either 3rd party, or the “Import from XML” transformation in EasyMorph.

Note that starting from v3.7 it will be possible to define connector names using a parameter, therefore the XML for the Import from DB transformation will look slightly different.

drbromley · December 2, 2017, 9:30pm

New to easyMorph and first time on the forum so apologies if this is already been answered. But the functionality of defining connector names is something I’m really interested in. When is version 3.7 expected?

dgudkov · December 2, 2017, 9:46pm

Hi @drbromley and welcome to the Community,

A beta of version 3.7 is already available on the download page: http://easymorph.com/download.html

The final release will be in around 3 weeks.

drbromley · December 2, 2017, 10:54pm

That’s great. Thanks for the quick response. Seriously impressed so far with the product.

drbromley · February 2, 2018, 2:19pm

Hi,

Is there any examples or tutorials available that demonstrate or detail how to define connector names using a parameter? I’m running 3.7.1.22 but I’m struggling to spot at the moment how I do this.

Cheers
David.

dgudkov · February 2, 2018, 4:16pm

Hi David,

Connector settings such as server URL or password or database name can’t be specified using a parameter. What can be specified is the name of connector to be used in a transformation.

For instance:

There are two connectors named “database A” and “database B” pointing to two different databases.

There is a parameter {PROD Connector} which current value is “database A”.

This parameter can be used in transformation properties instead of specifying the connector name explicitly. In the image below the name of a shared connector to use is specified using parameter {PROD Connector} therefore the transformation will use connector “database A”.

If you change the value of {PROD Connector} to “database B” then the transformation will use connector “database B”. If {PROD Connector} specifies a non-existing connector name the transformation will fail.

The option “Parameter (emb.conn.)” should be used when there is a need to specify an embedded connector using a parameter.

Furthermore, the table name itself can also be specified using a parameter (not used in the example).

Resume
One parameter can be used to specify a connector name.
Another parameter can be used to specify a table name (including schema, if necessary).

drbromley · February 5, 2018, 10:14am

Thanks for this Dimitry.

Got the export working by specifying the connector name as a parameter no problem.

However, I’m getting an issue when importing.

I have a calculated parameter named IMPORT_DATABASE_CONN that based on another parameter has a calculated value of DEV_DB.

I have a shared connector set-up called DEV_DB.

When I’m specifying the query in the query editor, everything works fine when using the IMPORT_DATABASE_CONN param - I can connect and view data and run queries no problem.