Data360 Analyze

Hi All,

We have connected to the oracle database for extracting the source file directly using the JDBC connection node. 

But we also want to have an alternate option of adding the source file manually using the excel node,  in case the connection fails to the database due to some reason. 

We tried using Switch node for alternating between the source files but it did not work out, since switch node always requires input from the 1st node. 

We used transform node method using Run time properties in which user can select DB or manual source file option but it is still not giving the option of alternating. 

Kindly check the attached file below and any help will be great. 

Attached files

Load DB or Manual.lna

Here is a method using a Data Flow property as the control. Note, you cannot use a Run property with this method.

A boolean type Data Flow property ('Use_DB_Source') is defined. 

The Data Flow property is referenced in the 'Enabled' property of the nodes in data source chains. In the upper chain the 'Use_DB_Source' property value is used to determine whether the nodes are enabled.

In the lower chain, the inverse of the 'Use_DB_Source' property value 

The outputs of the two chains are attached to a Connection Point where the connection filter is configured so that the first enabled data set is connected to the output of the Connection Point.

Attached files

Load DB or Alternate - 23 Feb 2021.lna

Hi Adrian,

Thank you for your help and this works perfectly in the dataverse 3.6 version. Since we are still using version 3.2 and will be switching to the latest version by May 2021.

Can you please recommend some solution for this issue in version 3.2.6.4596? It would be a big help for us

Here is the equivalent data flow for v.3.2.6.

The issue is that Connection Points were not supported in that release; so instead, the data flow uses a legacy Lavastorm Bypass node that is contained within a composite node. Legacy Bypass nodes could be imported into that release of Analyze but could not be edited - hence the need to include the Bypass node in it's own Composite node, which can then have connections made to its inputs and output. This works but is a bit of a hack. 

I strongly suggest you upgrade to a supported release as soon as possible.

Attached files

Load DB or Alternate_326 - 24 Feb 2021.lna

For completeness, here is a data flow containing just the Composite node with the legacy Bypass node

Attached files

Bypass_Composite_Node - 24 Feb 2021.lna

Hi Adrian,

Your solution perfectly works for us in the Development environment but once we push this into the UAT environment it does not work and gives error(attached below). This probably happens because of locked nodes and nothing can be edited.

Your solution does not work since we are using Data flow properties and the values do not flow because of locked nodes. But we do not see this issue with Run time Parameters at all.

Kindly check the below attached screenshot which includes the error we get in UAT and also screenshots from Dev and UAT environment. 

If there is another way of doing this then it will be really helpful since we are stuck with this issue from few weeks. 

Attached files

UAT error.JPG
Dev Node Toggle.JPG
UAT Node Toggle.JPG