What’s new in D365 2020 Wave 1 release for front-end developers

There are a lot of different blog posts and video reviews of features available as a part of the Dynamics 365 2020 Wave 1 release. I played with this release a bit and found 2 client-side code enhancements that can be interesting (or even useful) for developers. I wrote that Xrm.Navigation.navigateTo can be used to …

Continue Reading Andrew Butenko’s Article on their blog

What’s new in D365 2020 Wave 1 release for front-end developers

There are a lot of different blog posts and video reviews of features available as a part of the Dynamics 365 2020 Wave 1 release. I played with this release a bit and found 2 client-side code enhancements that can be interesting (or even useful) for developers.

Blog Syndicated with Andrew Butenko’s Permission

Author: Andrew Butenko

Share This Post On
468 ad

1 Comment

  1. It seems with this feature rollout, they broke the functionality of URL action if used to open a web resource (from a button). Technically, per MS’s documentation from 2016, URL action shouldn’t be used to open a web resource, but that doesn’t stop the fact that numerous blogs have been using it as a solution. Basically, if you’re passing anything except typename in the URL action, you’re going to get a 500 error. If you can’t wait on a fix, the solution (and only supported solution) is to use javascript action instead.

    I’ve seen this on any client that received the following solution updates:
    BaseCustomControlsCore v9.0.2002.1002
    CustomControlsCore v9.1.0000.13841

    (you can generally check CRM version, and if you see 13841, that client should be affected)

    MS is aware of the problem and currently working on fixes. If you’d like more details, you can contact me.

    Post a Reply

Leave a Reply