Skip to main content

Notifications

Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

OnChange Event does not get triggered when a field is updated by a plug-in

Posted on by 15

We have a plug-in that updates a field which triggers the OnChange event to call a JavaScript function. This works in the classic mode and also in the Unified Client Interface in an online instance. However, this does not work in the Unified Client Interface in an onpremise instance. Is this a bug or do we have to do something different for it to work in an onpremise instance?

  • Trillium Profile Picture
    Trillium 15 on at
    RE: OnChange Event does not get triggered when a field is updated by a plug-in

    Hi PG,

    The event triggers when I manually update the field, but we need it to be triggered when updated by a plug-in.

    Thanks,

    King

  • Trillium Profile Picture
    Trillium 15 on at
    RE: OnChange Event does not get triggered when a field is updated by a plug-in

    Hi,

    Thanks for your reply. We have customers who are on-premise only who may be using UCI. I guess we will wait for the next release of on-premise to see if it works with UCI.

    Thanks,

    King

  • Pankaj Gogoi Profile Picture
    Pankaj Gogoi 3,177 on at
    RE: OnChange Event does not get triggered when a field is updated by a plug-in

    Hi Trillium,

    Does it work if you manually change the value in the form? Can you check if the script file is loaded in the correct form in onPremise UCI.

    Best Regards

    PG

  • Suggested answer
    Henry J. Profile Picture
    Henry J. 5,237 on at
    RE: OnChange Event does not get triggered when a field is updated by a plug-in

    Hello,

    I'm not aware of that particular limitation, but please be aware that Unified Interface on Dynamics 365 Customer Engagement v9.0 on-premise is a very early version of Unified Interface.
    It is by nature very limited and it has a lot of known parity gaps or even issues that have only been fixed online.

    I'm curious as to why you would want to deploy Unified Interface on-premise and not use the web client instead?
    It's important that to consider that the web client on Dynamics 365 Customer Engagement on-premise is NOT deprecated.
    This is specifically called out here:
    https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/faqs-transition-unified-interface#how-does-this-move-impact-on-premises-customer-and-what-will-happen-when-the-web-client-is-deprecated-do-web-client-forms-become-unsupported
    So the web client will still be supported for them, as long as their on-premise version is supported.
    Support lifecycle for every product is detailed here: https://support.microsoft.com/en-us/lifecycle/search

    I would advise to wait for the next on-premise version to transition to Unified Interface on-premise.

    Henry

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans