Table Of Contents

XNET Database Merge (XNET Database Merge (Cluster)) (G Dataflow)

Last Modified: November 2, 2017

Merges all objects of the source cluster into the target cluster.

connector_pane_image
datatype_icon

wait for complete?

An input used to split the merging process into parts (for example, to display a progress bar).

datatype_icon

target cluster in

The I/O name of the cluster where the source cluster is merged.

datatype_icon

source cluster

The I/O name of the cluster to be merged into the target cluster.

datatype_icon

copy mode

An input that defines the merging behavior if the target cluster already contains elements with the same name.

datatype_icon

prefix

An input added to the source cluster name if an element with the same name exists in the target cluster.

datatype_icon

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

datatype_icon

percent complete

An output used when wait for complete? is false.

datatype_icon

target cluster out

A copy of target cluster in. You can use this output to wire the node to subsequent nodes.

datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Description

This node merges all objects contained in the source cluster into the target cluster.

The following nodes merge the objects with dependent-child objects:

  • XNET Database Merge (Frame)
  • XNET Database Merge (PDU)
  • XNET Database Merge (ECU)
  • XNET Database Merge (LIN Schedule)

Copy mode and prefix are passed to the appropriate node for the merging process.

If the copy mode is set to Copy using source or Merge using source, all cluster properties including the name are copied from the source to the target cluster.

Depending on the number of contained objects in the source and destination clusters, the execution can take longer. If wait for complete? is true, this node waits until the merging process gets completed. If the execution completes without errors, percent complete returns 100. If wait for complete? is false, the function returns quickly and percent complete returns values less than 100. You must call XNET Database Merge repeatedly until percent complete returns 100. You can use the time between calls to update a progress bar.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Supported

Web Server: Not supported in VIs that run in a web application


Recently Viewed Topics