Incorrect Level Displayed in Mapping #
Our mapping did not display the correct level hierarchy for the mapping record. For example, ‘Account’ is the first level, and ‘Contact’ and ‘Contract’ are child of ‘Account’. However, ‘Contract’ was displayed incorrectly and appeared under ‘Contact’ instead of ‘Account’. This issue has been resolved.
Second Workflow Errors Caused by ‘What to Do with Failed Messages?’ Interface Setting in Batch Processing #
We had a problem with the second workflow of batch processing because the option ‘Overwrite failed message and delete pending’ was set, which caused the second workflow to encounter an error. However, we have resolved this issue now.
Not able to be saving the mapping #
An error occurred while attempting to save many mapping records, resulting in the following error message: ‘Apex CPU time limit exceeded: Error is in the expression ‘{!saveMapping}’ in page skyvvasloutions: sc_mapping: (skyvvasolutions).’ This issue has been resolved by reducing the query record of object ifunction__c and reducing calling getFields(IMapping__c m).
