Notifications

21 views

Description

In a scenario with uni-directional change integration, where a change is created on the other side and it should sync with your instance. All is correct when we select a planned start and end date 2-3 days in the future from the creation date.

If the planned start/end date goes more than 3-4 days from the creation date it throws the error. "Operation against file 'change_request' was aborted by Business Rule 'Transform synchronously'"

Release or Environment

Madrid, New York

Cause

Date Format.

Resolution

The root cause of the issue is with the Date format of the Transform Map which is being used to create the Change Requests.

The date format of your <instance> is set as: 'dd/MM/yyyy' and so the system is expecting the date to be set with the same format.

But on the Transform Map: '<transform map name>', /nav_to.do?uri=sys_transform_map.do?sys_id=2956bd5c1b48cc9039bea938bd4bcb81

The mapping between fields: Start date and End date are configured to set the date format as: 'yyyy-MM-dd hh:mm:ss'

  • /nav_to.do?uri=sys_transform_entry.do?sys_id=ffc835d01b88cc9039bea938bd4bcbb2
  • /nav_to.do?uri=sys_transform_entry.do?sys_id=70e875d01b88cc9039bea938bd4bcb5d

This is the reason why the import set is failing with the business rule: "Transform synchronously".

To fix this issue, the System Time format should be set to: 'yyyy-MM-dd' or the date format on the field mapping in the Transform maps should be set to whichever format the system is expecting.

Article Information

Last Updated:2019-11-04 06:44:26
Published:2019-11-04