We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.
Our Support systems migrated on Saturday, May 21. We'll automatically forward you to the new location for this content.

Articles in this section

See more

Data3Sixty® Analyze 3.5.1 is Now Available

Avatar
Adrian Williams
  • Updated
Follow

infogix_logo.png

mceclip0.png 

ATTENTION: In order to continue receiving product update notices, please Sign In and select “Follow” on the Data3Sixty Analyze announcements page here.

 

Infogix are excited to announce the availability of Data3Sixty Analyze 3.5.1 which includes several new features to explore.

Product downloads are available within our Data3Sixty Analyze Download section.

 

What’s New?

This month we’ve made several enhancements to Data3Sixty Anakyze including improvements in the detection of semantic types and greater flexibility when querying databases.

 

Node Enhancements

Reorder Fields Node Node

The Reorder Fields node enables you select the fields, and set the order in which fields appear in the output data set. 

Reorder_Fields_Node_All.png

Typically the Reorder Fields node is used before a publishing node (e.g. the Output Delimited node). Note: Data3Sixty Analyze does not guarantee field order of intermediate data when it is processed by subsequent nodes.

You can search the input fields to highlight those that contain the specified characters. The Next Match up-/down-arrows allow you to step through the matches in the field list.

Reorder_Fields_Node_Search_Fields.png

You can search the input fields to highlight those that contain the specified characters
The ‘Move Up’ / ‘Move Down’ arrows, and the ‘Move to Top’/ ‘Move to Bottom’ buttons allow you to change the positioning of the selected field. Multiple fields can be selected using <Shift>+click and <Ctrl>+click combinations.

mceclip0.png

You can exclude selected field(s) from the output data using the ‘Remove Fields’ button. 

When one or more fields have been removed, the ‘Add Fields’ button is enabled. The Add Fields pop-up panel is displayed when the button is clicked.

You can reset the field order to that of the input data using the Reset button.

mceclip1.png

The Add Fields panel provides a two-pane layout with the fields that are available to be added on the left. 

mceclip2.png

The move field controls can be used to add fields to and exclude fields from the output, and to reorder the selected fields. You can search for fields in the Available Fields and Selected Fields panes. You can also select all fields or deselect all fields using the Select All and Select None buttons.

The FieldsNotExistsBehavior property controls whether the node the node generates an error/warning if the input data does not contain fields specified in the Field Order property.

mceclip3.png

You can choose to generate an error (default), log the warning or ignore the condition. Setting the property to Ignore (or Log) can be useful when your input data can contain optional fields and you want to specify the order of the fields when they are present but not generate an error when they are absent.

mceclip4.png

 

JDBC Nodes

The JDBC Execute, JDBC Query and JDBC Store nodes now allow you to specify key=value pairs on separate lines. 

mceclip5.png

You can still specify the options on a single line as an ampersand delimited list.

mceclip6.png

 

Salesforce Nodes

The Data3Sixty Get for Salesforce, Data3Sixty Metadata for Salesforce and Data3Sixty Update for Salesforce node now use v.46.0 of the Salesforce REST API.

The Data3Sixty Update for Salesforce node offers the following enhancements:

  • The node provides the option to continue processing input records when a Salesforce update transaction has failed. Records for the failed transactions are output on the new ‘errors’ pin'. The ‘ErrorBehavior’ property enables you to specify the action taken when a transaction fails (default is to error).

mceclip7.png

  • If no value is provided for the ‘IdField’ property, the property defaults to “Id”.
  • If no fields are specified in the ‘DataFields’ property, the fields will be taken from the headers.

mceclip8.png

 

Encrypt Fields and Decrypt Fields Nodes

The Encrypt Fields node now supports the use of the AES 256 encryption algorithm. The new ‘Encryption Type’ property sets the algorithm to be used by the node. For backwards compatibility reasons, the default algorithm is Triple DES encryption.

mceclip9.png

 

The Decrypt Fields node now supports the decryption of fields that have been encrypted using Encrypt Fields node and the AES 256 algorithm.

 

BRD File Node

The BRD File node provides two additional properties:

  • PassThroughFields - This property specifies the fields that are to be passed through to the output. It provides a choice of All/Used/Unused/None. The default is None.
  • AlwaysEmitPassThroughFields - Controls whether the input fields will be passed through to the output even when a BRD file contains no records. The default is False.

mceclip10.png

 

Fixed Format File Node

The Fixed Format File node now supports the optional ‘StartLine’ property. The property enables you to skip lines at the start of a file.

mceclip11.png

 

Application Enhancements

Connection Points

mceclip12.png

Connection Points can be used to:

  • Include multiple data sets in a bundle to reduced visual clutter on the canvas
    • Tags are used to identify the data in the bundle
  • Pass the first enabled data set into a node’s input pin
    • You can specify the order in which the input data sets are evaluated

mceclip13.png

 

A Connection Point can be added to the canvas using the right-click context menu.

mceclip14.png

Multiple connections can then be made to the Connection Point. When source data is available, hover text indicates the number of records available in each input data set.

mceclip15.png

You can add a name tag to the Connection Point. 

mceclip16.png

Adding a name tag can help with identifying data sets. 

mceclip17.png

The tags for the individual data sets will include the name tag configured for the Connection Point and the name of the data set – as determined by the output pin of the upstream node. When using Connection Points, Infogix recommends changing the names of output pins to have descriptive names. Additionally, a number of default output pin names have been renamed to help you to identify the source node, for example, the Sort node output pin has been renamed from "out1" to "Sorted Data".

A connection filter dialog is displayed when a connection is made from the Connection Point to a downstream node that can accept multiple data sets (e.g. a Cat or Composite node).

mceclip18.png

You can choose to propagate:

  • All the data sets
  • Specified data sets (using their tag)
  • The first enabled data set

mceclip19.png

When the cursor is hovered over a data set tag the corresponding connection is highlighted to assist with its identification.

mceclip20.png

When a connection is made to a downstream node that can accept a single data set (e.g. a Transform node) you can choose to propagate:

  • A single data set (using its tag)
  • The first enabled data set – a index indicates the order in which the data sets are evaluated.

mceclip21.png

You can modify the settings for a connection filter by clicking the button on the connection.

mceclip22.png

Connection Points can be chained together, enabling you to include other data sets into a bundle at a later point in the data flow.

mceclip23.png

 

Navigation Improvements

You can now right-click on a node’s input pin or an output of a Composite node to display the ‘Go to Linked Item’ menu option. 

mceclip24.png

When the menu option is clicked, the UI navigation changes to display the source of the data. The displayed layer of the canvas also changes if the source is on another layer – i.e. within a Composite. 
The navigated-to data source will be the connected node or, an intervening Connection Point that has multiple input data sets.

 

Database Drivers

The application now includes the JDBC driver for the IBM DB2 database.

mceclip25.png

 

Properties Panel Python Script Editor

The Python script editor has been changed to better conform to the Python style guide. The script editor in the node properties panel now auto-indents text using four Spaces characters. The editor also converts Tab characters to four Space characters.

mceclip27.png

 

Run Properties

The Current* data flow properties are deprecated in this release, i.e.

  • CurrentTime
  • CurrentDateTime
  • CurrentDate


Instead, the RunTime, RunDate and RunTimeZoneOffest properties should be used for new projects. The corresponding system property references can be used in property values and scripts. See the ‘Run Property Substitution’ topic in the Help for further details, or online here.

 

Resolved Issues

The following issues have been resolved in this release:

LAE-9544, LAE-9858, LAE-10236, LAE-10518, LAE-10520
LAE-10791, LAE-21607, LAE-21612, LAE-21688, LAE-21830
LAE-21833, LAE-21839, LAE-21857, LAE-21869, LAE-21897
LAE-21905, LAE-21916, LAE-21919, LAE-21923, LAE-21931
LAE-21936, LAE-21939, LAE-21941, LAE-21955, LAE-21956
LAE-22000, LAE-22015, LAE-22022, LAE-22035, LAE-22082
LAE-22120, LAE-22179, LAE-22200

 

See the release notes for details of the resolved issues.

 

For more about this release view the release notes. And don't forget to check out the Community to get your questions answered or to give us feedback.  We love to hear from you.

Related articles

Comments

0 comments

Please sign in to leave a comment.