DESCRIPTION FOR RELEASE NOTES:
Incorrect Auto Numbered ID format on a custom sub-object when a record instance of the sub-object is being copied on the MUX
SUMMARY:
A custom sub-object on MUX, has the attribute ID (code) as auto-numbered. In the auto-numbering segments, there is a reference to its Parent Object attribute. This Parent Object Attribute reference is the ID (code) field on the Parent Object which is also auto-numbered. On the Child object if an existing record instance is being copied, then the auto-numbered generated ID, is incorrectly formatted and referenced
STEPS TO REPRODUCE:
1 On the Classic UI create a custom Master Object which is not referenced to investment extension
2 On the Parent custom object, configure the field: ID (code) to have auto-numbering, as show in the screenshot
3 On the Classic UI, create a sub-object of the master object which is created on Step 1
4 On the sub-object configure the attribute: ID (code) to have auto-numbering as mentioned below:
5 Navigate to the MUX and make a copy of the auto-generated blueprint for the custom Master Object. Add the sub-object module to this blueprint and publish the changes. Make this blueprint as the default blueprint
6 Navigate to the custom object workspace of the MUX and create a master record
7 Once the master record is created, create a record for the sub-object
8 Copy the created new sub-object record instance, by right clicking on the record and choosing copy option. The instance could be copied in either way, i.e. from the shortcut menu or from the "Copy" button on the context menu:
Expected Results :-
A copy of the exiting sub-object record should be created with the attribute: ID having valid auto-numbered value, as per the configuration
Actual Results :-
A record is created with the auto-numbered incorrectly displayed, as the Parent Object Attribute Reference ID is displayed instead of the attribute value. For example: C00000001/{mst0001.code}. When the sub-object's record instance is created the Parent's ID is correctly referenced, as per the auto-number configuration, for example, refer to the first record on the below screenshot: C00000001/P00000001
This was originally tracked as DE77720 and is resolved in 16.2.0.