Not able to be saving the mapping #
An error occurred while attempting to save the mapping records, which resulted in the following error message: ‘928 >> System.DmlException: Upsert failed. The first exception occurred on row 7, with the following error: DUPLICATE_VALUE. A duplicate value was found for the skyvvasolutions__ExtID__c field on a record with the ID xxxxxxxxxxxxxxxx. This was due to mapping the same attribute fields to the same target/source fields multiple times. However, this issue has now been fixed.
Getting Issue Cannot Update Standard comment #
There is an issue while you have used the Operation Type Apex class function in order to override message comments. Since it still uses the standard comment instead. This issue has been fixed.
The Formula Cannot Retrieve the Field Value #
The formula function was unable to retrieve the value from the ‘Field’ due to white spaces at the start and end of the field, while there was another field inside the formula that had a relation with a dot. For example, in the formula IF(FieldA = ‘xxx’, FieldB.FieldC, FieldD), FieldA was unable to trim the white spaces, resulting in an issue. However, this issue has been resolved.
Fixed the Issue of Duplicate Name Creation for Connection Destination in the New Agent #
There is an issue when the user creates multiple connection destinations with the same name, as it will only display one connection destination even if there are multiple. Therefore, we are no longer allowed to create duplicate names.
Fixed Various Issues on Mapping Tool #
- The fixed outbound mapping now allows fields to be mapped directly without a parent node
- Previously, there was an issue re-generating sequence when mapping a source node to multiple target nodes in outbound mapping. However, this issue has been resolved.
- The problem of deleting a mapping record and unintentionally deleting other sibling records has been fixed.
- Fixed the ordering of mapping records based on the Target Node records in outbound mapping.
- The issue of the mapping tool generating an incorrect tree mapping view of the outbound mapping has been fixed.