Home Support NI Product Manuals SystemLink 19.6 Manual

Table Of Contents

Configure Retention (Duration) (G Dataflow)

Download Manual | Offline Viewer Required
Version:
    Last Modified: November 18, 2019

    Creates a retention policy for historical tag values to expire after a set number of days they were written.

    connector_pane_image
    datatype_icon

    tag in

    Reference to a tag on the server.

    Use Open Tag or Query Tags to obtain this reference.

    datatype_icon

    days

    The number of days tag values stay in the tag history before they expire.

    The default is 30 days.

    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

    tag out

    Reference to a specific tag on SystemLink Server or SystemLink Cloud.

    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.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Not supported

    Web Server: Supported in VIs that run in a web application

    Recently Viewed Topics