[Bug] setDefaultView is not working in the Unified Interface
Recently, there is an issue in Unified Interface where setDefaultView Client API in JavaScript is not working even though the same script is working for the same form in the legacy web client.
formContext.getControl(“parentaccountid”).setDefaultView(“{00000000-0000-0000-00AA-000010001031}”); // GUID of Inactive Accounts view
After raising a ticket with Microsoft, the issue had been concluded as…
Continue Reading noreply@blogger.com (Linn Zaw Win)’s Article on their blog
[Bug] setDefaultView is not working in the Unified Interface
Recently, there is an issue in Unified Interface where setDefaultView Client API in JavaScript is not working even though the same script is working for the same form in the legacy web client. formContext.getControl(“parentaccountid”).setDefaultView(“{00000000-0000-0000-00AA-000010001031}”); // GUID of Inactive Accounts view After raising a ticket with Microsoft, the issue had been concluded as a product bug by the “Product Team” and the following workaround solution is provided.
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