Troubleshoot Label Data Sources

One of the following approaches may resolve the issue:

• Check each property of the field that has the potential to limit the length of the data. For example, if a text field refers to a label data source, you must ensure that the Chars Per Line, # Lines, and Max Chars for the field are great enough to accommodate the expected data. Similar properties exist for Barcode fields. For Text Box fields, printed data can be truncated by the Text Box Overrun Mode. For more about this mode, see User Interface: System.
• If the label data source is a Date/Time data source, an administrator should confirm that the clock on the Loftware Application Server is set correctly.
• If you are running a custom process, an administrator should verify that neither the process nor a business rule is overriding the label data source or affecting the output in an unanticipated manner.

The following factors can affect the how text in a Text Box field is displayed:

• Data in a Text Box field automatically wraps at the end of each line if the text would otherwise extend beyond the envelope of the field. When line wrapping occurs, the line break is either at the end of a word or after a hyphen, en-dash, or em-dash. If a word is too wide to fit in the field, a line break occurs within the word at the edge of the envelope.
• If more data is received for a Text Box field than will fit, the Text Box Overrun Mode determines how Loftware Enterprise SP responds. However, this mode can be configured in multiple places. For information about precedence when it is configured in multiple places and about the available values, see User Interface: System.
• If enabled, Dynamic Font Sizing can alter the font size and aspect ratio of characters. For more information, see the Font section in Text Properties.

If the Data Service Administrator deletes a custom parameter in the JDBC data service, that parameter is automatically removed from the associated data sources. For more information about the behavior to expect, see Managing Data Service Parameters.

Any Database data source or Alternate data source used in a label template that must support on-demand printing must have at least one trigger A means of running an action, rule, or data service. Includes a trigger source if interactive (such as a button, a prompt, or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.. If the data source must support both on-demand printing and integrations, then it must have at least two triggers, including one with a Do Not Run trigger source. If the data source does not need to support on-demand printing, then no triggers are required. For more information, see Controls, Actions, and Triggers.

If the label template must support on-demand printing and includes a Database data source and an Alternate data source (or more than one of either), review the triggers for the data sources. Determine whether triggers with the same combination of trigger source, trigger event, and trigger key (if any) are used by more than one data source in the label template, regardless of the type of data source. If so, it may be necessary to configure values for priority The order in which actions, rules, or data services that have otherwise identical triggers are run. Priority values are compared only if the actions have the same trigger source, trigger event, and trigger key (if any). The type of trigger source is irrelevant. Among actions, rules, or data services with otherwise identical triggers, the trigger source with the lowest value for priority is run first. to manage the order in which the data sources are run. For more information, see Controls, Actions, and Triggers.

The dialog box displays only Database data sources and Alternate data sources for which the selected field or form has is not already configured as a trigger source.

• In the Properties pane, you can confirm whether a trigger already exists for the data source.
• In the Data Sources pane, you can confirm whether a particular data source exists.

Some drivers provide native support for Inc/Dec behavior, which may improve performance. To optimize performance, ensure that the Minimum Value and Maximum Value include the same number of digits. The Minimum Value can be padded with leading zeros.