1. NiceLabel Help Center
  2. Designer Pro / PowerForms
  3. How-To and Reference Articles

Importing Variables from Legacy Labels

The legacy label format (.LBL) is supported by NiceLabel 10. This means that labels that have been created using the NiceLabel V6 can be imported into NiceLabel 10 along with their variables.

Generally speaking, imported variables with matching names from legacy label files are merged with variables on labels created using NiceLabel 10. Because you might come across issues with variable importing, please read the below listed rules under which the variables are imported and integrated into a .NLBL label file.

Tip

Merged variable is a variable that displays the value after the import from Desktop Designer V6 to NiceLabel 10 label file.

Merging variable is a variable that is imported to NiceLabel 10 label file.

Original variable is a variable in NiceLabel 10 label file.

  1. Variables with matching names are merged in a NiceLabel 10 label file in the following cases:

    • Data Type of variables (Text, date, Time, etc.) is the same.

    • Variable values are equal.

    • One of the variables is a Counter.

    • Variables have either defined fixed length or not.

  2. Variables with matching names are merged with a reported conflict in the following cases:

    • Input formats, dynamic values, prefix/suffix, or padding types/values of variables are different.

    • Length of variable values is defined as fixed. In case of non-matching lengths of values, merged variables report a conflict.

    • Variables have multiline values. With non-matching number of lines, line length, or word wrap, merged variables report a conflict.

    • Min and max values of merged variables do not match.

  3. Counters with matching names are merged with a reported conflict in the following cases:

    • Step, count, and increment type do not match. Merged variables report a conflict.

    • Differences in rollover settings: min/max value, counter type, rollover on variable change, variable reference, date/week rollover type, day rollover time. In case of non-matching values, merged variables report a conflict.

    • Printer counter is enabled. If the internal counter types do not match, merged variables report a conflict.

  4. General rules for conflicting values of merged variables.

    • The value of the original variable is used for prefix, suffix, and padding. If these values are empty, the value of the merging variable is used instead.

    • If one of the variable values is dynamic, the merged variable displays the dynamic value.

    • If the variables have values with fixed lengths, the higher value is assigned to the merged variable.

    • If one of the variables has enabled a multiline value, its value is assigned to the merged variable.

    • If the variables have defined line length and a number of lines, the higher value is assigned to the merged variable.

    • If one of the variables has enabled word wrap, its value is assigned to the merged variable.

    • If both variables have defined min and max values, the merging variable value is assigned to the merged variable. If not, the original value is used instead.

    • In case of non-matching counter values, the value of the merging variable is assigned to the merged variable.