Microsoft Unified Interface does not fire an onChange or onLoad event when a field is updated from a real time workflow.

(0) Share

Report

Posted on by StingRayYellow05

Hello.

I have a Dynamics 365 org (9.1.0.3063) where I update a field on a form, which triggers a real time workflow. The completed workflow updates another field on the form, which we use to execute JavaScript to set the form notification. This process works well with the default web app, but does not work with the new Unified Interface. My testing shows that updating a field with a real-time workflow does not fire the field's onChange or the form's onLoad events.

Can anyone confirm they are experiencing this as well, and perhaps offer a workaround?

Thank you for reading.

Ref: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/clientapi/reference/events/attribute-onchange

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (1)

gdas 50,091 Moderator on at

Like (0)

Report

Hi,

This is normal , when you update any field value using real time workflow it's basically changes the data in server side and JavaScript field on change event trigger in the client side . So there is no chances to work on change event of the field while updating field using RT workflow.

Was this reply helpful? Yes No
Verified answer

Kokulan 18,054 on at

Like (0)

Report

Hi

What is the version of Server and Client?

I have tried this on Server version: 9.1.0000.3647Client version: 1.3.1576-190329-042235, and the onChange event fires.

Here is what I did, a real-time workflow that triggers on Change of Email field on the contact and the workflow then updates the Mobile Phone field with Process Execution Time.

On the form, I had both form load and mobile phone field change event wired displaying an alert with the respective event message.

And the onchange event on mobile change actually fires after RTWF updated the value.

Your OnChange may not be firing for the following reasons.

01. Your script is not on the form that is rendered by Unified Interface - depending on the version of crm, Unified Interface may be rendering the Interactive Experience form but you have the script on the normal Main form that's why it works on Classic UI not on UCI

02. Check there are no script errors in developer console in the browser

03. Do you have any Business Rule bound to that field that has this onChange event wired?

Was this reply helpful? Yes No
StingRayYellow05 10 on at

Like (0)

Report

Thanks for the feedback.

I tested a similar process in another environment, and experienced the same results.

Here’s what I did:

1. Opened a record in the web app (original interface)

2. Manually changed a value in a field, and verified the onChange event fired.

3. Manually changed a value in the same field, and verified the onChange event fired again.

4. Opened a record in the unified interface (new interface)

5. Manually changed a value in a field, and verified the onChange event fired.

6. Manually changed a value in the same field, and verified the onChange event did NOT fire.

It seems like the Unified Interface only supports firing the onChange event ONCE, as opposed to the classic interface firing onChange events multiple times.

I wonder if this is a bug with the new UI, or a change in the way that Microsoft is addressing these events.

If anyone has a workaround (outside of reloading the record) please let me know.

Was this reply helpful? Yes No