Planned Start and End dates are incorrect on change form created from a record producerIssue In this scenario the customer is using a record producer to create their Change records. The Planned Start and End dates entered on the record producer are incorrect/do not match the Planned Start and End dates on the Change form that is created.ReleaseOrlandoCauseThere was customisation in place that caused the values to be incorrectly calculated. (a business rule and a custom script in the dictionary of a custom field.) The fields on the record producer were also incorrectly mapped to the fields on the Change form The data type of the variable on the record producer was different to the data type of the field it was mapped to.ResolutionThere were multiple configuration issues causing different issues with the Planned dates. I noticed that when raising from native UI change form the planned dates are populated correctly. The issue only happens when using the record producer:Radian service catalog > account management > Firewall Change request issue 1. End date was being recalculated to exactly an hour from the start date. Debugging showed a custom business rule "Planned End" runs. Disabled this business rule but the dates are still incorrect Found further customisation that was calculating the value for a custom field "u_calculated_end _date" being referenced by the BR Checked the dictionary for the custom u_calculated_end_time field and found a script that sets the value of the custom field "u_calculated end time" to exactly 1 hour from the Planned start time by adding 3600 seconds. The custom business rule "Planned End" then sets the Planned end date field to the calculated value in "u_calculated_end_date" ***Disabling the customisations fixed the first issue but the dates were still not matching. Issue 2. The dates were still not matching what was being selected on the RP The Planned start date on the change form always matches what was entered in the "Requested Implementation Date and Time" variable on the record producer. This is expected because on the record producer the variable "Requested Implementation Date and Time" was mapped to the "Planned start date" on the change form. The variables on the portal form (RP) were not mapped correctly to the fields on the UI Form *** Fixed the issue with the mapping by checking that all the variables were mapped to the correct fields. ie. Planned start to Planned start Issue 3. The final issue is that the dates populated on the Change form are changed to exactly a day before on the dates selected on the Record Producer. Checked and found the data type for variables Planned Start and End is of type "Date" and on the form, the field it is mapped to is of type "Date/time" *** Changed the variable data type to the same type as the form field, i.e. Date/Time and the Planned dates on the change form are now the same as what is selected on the record producer.