With the deprecation of Xrm.Page.context.getQueryStringParameters, Microsoft Docs article suggested using formContext.data.attributes API to make retrieval of non-entity bound data consistent across entity forms.
But some of the sample codes that I found online are all using the deprecated Xrm.Page.context.getQueryStringParameters and some are using…
Continue Reading noreply@blogger.com (Linn Zaw Win)’s Article on their blog
Pass Parameters to Quick Create Form in Dynamics 365 using formContext.data.attributes
With the deprecation of Xrm.Page.context.getQueryStringParameters, Microsoft Docs article suggested using formContext.data.attributes API to make retrieval of non-entity bound data consistent across entity forms. But some of the sample codes that I found online are all using the deprecated Xrm.Page.context.getQueryStringParameters and some are using undocumented Xrm.Utility.getGlobalContext().getQueryStringParameters().
Blog Syndicated with noreply@blogger.com (Linn Zaw Win)’s Permission
More About This Author
Array
- Dyn365CE4 March 2024Open New Record Form with Pre-populated Fields Using Xrm.Navigation.navigateTo
- Dyn365CE23 February 2024How to Fix Button in Modern Command Bar Disappearing After Grid Item Selection
- Dyn365CE16 February 2024Keep Your Dataverse Solution Clean and Simple
- Dyn365CE7 February 2024Refresh Main Form When New Child Row is Added in Subgrid via Quick Create Form in Model-Driven App