Field values set by the script in the Record Producer are getting overridden by a "before insert" Business RuleIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } The fields on the target record are not being populated with the dynamic values set in the record producer script. Instead, those are being populated by some other value at the 0th update itself, which is causing unexpected behavior and inconsistencies in the data. The script written in the record producer is not functioning as intended, leading to issues with data population and potential errors in the system. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } All Releases Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Please check if there are any "before insert" Business Rules on the target table that may be overriding the field values set by the Record Producer script. For context, here’s how the flow works when a Record Producer is used: The user submits the Record Producer form.The Record Producer script runs, populating values on the current record (e.g., sn_customerservice_case, incident, etc.).This happens before the record is inserted into the database. Once the record is saved, Business Rules on the target table are triggered in the following order: - Before Business Rules (e.g., validations, assignments) - After Business Rules (e.g., notifications, integrations) - Async Business Rules (e.g., logging, external API calls) So, the logic in the Before Business Rules can override the values set in the Record Producer script. You may want to add appropriate conditions to those rules to avoid unintentionally resetting values already defined. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } To resolve the issue of field values set by the Record Producer script being overridden, please follow the steps below: Review the custom Business Rule (BR):Check for any before insert Business Rules on the target table that might be modifying fields like Short Description.Modify or disable the BR:If the BR is unintentionally overriding values set in the Record Producer script, update its conditions or logic accordingly. Alternatively, disable it if it's not needed.If the issue persists:Verify that no other Business Rules, UI Policies, or scripts (including Flow Designer actions or Script Includes) are affecting the field values.