LX_FAN - Alternate Names

A list of the Alternate Object Names for an object.

It contains the Long Name of an object. It is exported and imported with an Object. When an object is created the Long Name is checked in this table for uniqueness. The Long Name can be changed, unlike the Short Name.

When importing and the Long Name already exists for another object a warning is issued and the Long Name is lost. The object will need to be edited and another unique long name added to it.

13.0

LX_DTA

No

LX_FAN_PRIM

Y

XANP_I, XANTYP, XANOBJ, XANEXT, XANEX2 

LX_FAN_I1

Y

XANP_I, XANUNQ

1

XANP_I

Partition Identifier

CHAR(3)

2

XANTYP

Object Type

CHAR(2)

3

XANOBJ

Object Name

CHAR(10)

This is the name by which the object is known in the table specific to its object type. It is a foreign key into that table. E.g. For a Component it is the X03FLD value. At the time of creation of the object, this value is also unique across ALL object types in a Partition. It may be possible that an import or a Check Out breaks this rule. Therefore the uniqueness is not enforced in the database for this column by itself; its enforced only in conjunction with the Object Type.

For newly created objects in an RDMLX partition, this value is a maximum of 8 characters and only consists of valid C identifier characters.

4

XANEXT

Object Extension

CHAR(10)

Not currently expected to be used as Multilingual Text Variables will probably not support longer names. 15 characters of difference (*MTXT…) is considered sufficient.

5

XANEX2

Object Extension 2

CHAR(10)

e.g. Logical View Name

XANUNQ

Object Unique Name

CHAR(128)

The object's long name is only unique in the first 128 characters. The remaining characters are for information only. This value is held in upper case e.g. AUNIQUELONGNAME

XANLNG

Object Long Name (As visualized)

STRING(256)

The entire Long Name in the case that it was entered by the user e.g. AUniqueLongName