PowerApps – Page 5 – Nishant Rana's Weblog

Try the new modern look for the Model-driven app (Preview)

The new modern refreshed look for the Model-driven app can be enabled from Maker Portal >> Model-driven App (Edit) >> Settings >> Upcoming – Try the new look and feel (preview)

The new look makes use of the latest Fluent UI React Components

Or now we see the option to Try the new look in the app itself in the command bar.

Let us look at the changes

Grids now have the checkboxes added to it

(open the image in new tab to view it clearly)

Infinite scrolling

The same grid is applied to Sub Grid and Associated Grids

Forms now have a new Command Bar, refreshed BPF, Sections, etc.

Form fields now have a background, icon placement, stying changes, etc.

Get all the details here

Hope it helps..

Advertisements

Interesting articles on Plugin behavior – Dynamics 365 / Dataverse

Found below interesting articles, do check out-

Can we create child records in Pre-Operation Plugin?https://community.dynamics.com/forums/thread/details/?threadid=1e757e7a-60b2-4fc6-9a94-acea44b18f8c

What happens when we use ExecuteMultiple within Plugin?https://www.inogic.com/blog/2015/11/executemultiple-workflow-or-plugin-assemblies/

Advertisements

Set DefaultSelectedItems of Combobox on App OnStart – Custom Page -Power Apps (Dataverse)

Recently in one of our custom pages, we had to set the default value (DefaultSelectedItems) of the combo box based on one of the lookup fields on the record. We were opening the custom page from the ribbon button on the form.

Below is our function to pass the record’s GUID to the custom page from the button.


    openSearchCustomPage: function (primaryControl, firstPrimaryItemId) {
        var pageInputCustom = {
            pageType: 'custom',
            name: 'custom_searchproduct_570ed',
            entityName: 'lead',
            recordId: firstPrimaryItemId
        };

        var navigationOptions = {
            target: 2,
            position: 1,
            width: 1350
        };

        Xrm.Navigation.navigateTo(pageInputCustom, navigationOptions).then(
            function success(result) {
                console.log(result);
            },
            function error(error) {
                console.log(error);
            }
        );
    }

Next in App’s OnStart, we are setting the GUID of the record to a variable first, and than setting another variable to store the GUID of the Region lookup field on that record.

// text variable passed by the form / webresource/ ribbon
Set(varEnquiryIdWithoutCurlyBraces,GUID(Substitute(Substitute(Param("recordId"),"{",""),"}","")));

// get the Region Of Interest from the Lead / Enquiry ID
// If value present use it for prefiltering the Gallery Items
Set(varRegionOfInterest,LookUp(Enquiries,Lead=varEnquiryIdWithoutCurlyBraces, 'Region of Interest'));

And lastly, for the combo box (Items = Region (custom table)), we are setting the DefaultSelectedItems as follows

LookUp(Regions,Region=varRegionOfInterest.Region)

We also tried using the Filter option, but it was giving incorrect values.

The value on the form –

The value in the Custom Page –

Correct value populated for combo box Region, and incorrect for the one using Filter formula

Hope it helps..

Advertisements

Fixed – View Name as Blank in Dynamics 365 / Model-driven app

Recently we faced an issue where one of the views was not showing its Name in the app.

On selecting the View Selector, we were not getting the option to select that view.

Checking in a Vanilla CRM instance, we can see it is OOB My Activities view.

To fix it, we had to edit the App, Add Page >> Dataverse Table >> Select exiting table >> Activity

And add that view to that app and publish the changes.

The result –

Hope it helps..

Advertisements

Fixed – Expected non-empty Guid while importing solution in Dynamics 365/ Dataverse

While trying to import the solution (patch), we were getting the below error.

“Expected non-empty Guid”

There was hardly any detail in the log file also

We tried removing the solution component one by one in our source environment and trying the import again in the target environment.

Eventually removing the Pages (custom page) allowed us to import the solution successfully into the target environment.

We then compared the customization.xml of the current solution with the backup solution of the Target and see the information missing in the current solution.

Left is – Current solution (giving error) and Right is the backup solution of the target.