In the clarity system we have a custom object with ID attribute set as auto-numbered. While trying to XOG-OUT and XOG-IN of the custom object instances, we find that the auto-numbering schema set on the object is not considered, is there a way for the XOG file to consider the auto-numbering format of the ID attribute by specifying it in the instancecode paramater?
16.0.2 and All releases
XOG-IN (or write) the custom object instance by using the following XML tag:
NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_customObjectInstance.xsd">
<Header action="write" externalSource="NIKU" objectType="customObjectInstance" version="16.0.1.838">
<args name="overrideAutoNumbering" value="false"/>
</Header>
<customObjectInstances objectCode="neo">
<instance instanceCode="-1" objectCode="neo">
<CustomInformation>
<ColumnValue name="code">-1</ColumnValue>
<ColumnValue name="name">Instance 1</ColumnValue>
<ColumnValue name="odf_period_end"/>
<ColumnValue name="odf_period_start"/>
<ColumnValue name="page_layout">odf.neoFrame</ColumnValue>
<ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
</CustomInformation>
<OBSAssocs complete="false"/>
<Security>
<UserSecurity rightCode="odf_cst_neo_edit" userName="admin"/>
</Security>
</instance>
</customObjectInstances>
</NikuDataBus>
The flag overrideAutoNumbering is defined on the XOG header and determines whether source XOG content overrides auto-numbering in the target content. The flag is available for the custom attributes of stock and custom objects.
The following rules apply: If the flag is set to TRUE, XOG content from the source is applied to the target. If the flag is set to FALSE, the auto-numbering scheme defined on the target is applied. The flag is specified in the XOG export file. By default, OverrideAutoNumbering=TRUE.