PowerApps – Page 41 – Nishant Rana's Weblog

What is the maximum file size limit for Attachments in Dynamics 365 \ On Premise V9?

Recently was trying to figure out the maximum file size limit for the attachments.

It is 131072 (in kilobytes)

Can be defined at Settings – Administration – Email Tab.

Scroll down to Set file size limit for attachments section

MaxSize

Hope it helps..

How to – Use SARIF Viewer to read the static analysis results generated by Microsoft.PowerApps.Checker.PowerShell module

In the last post, we saw how we can use the Microsoft.PowerApps.Checker.PowerShell module to analyze the Solution (Unmanaged and Managed – Online or On-Premise) outside the PowerApps Maker Portal.

https://nishantrana.me/2019/07/12/using-the-powerapps-checker-powershell-module-to-validate-the-solution/

The reports generated by the tool are in SARIF format i.e. Static Analysis Results Interchange Format (JSON based) standard for the output format of the static analysis tool. This format originated at Microsoft.

To view the result, we can use the below tools

For Visual Studio :

After installing the extension, navigate to Tools à Import Static Analysis Log files for Error List à Import SARIF file and select the result file generated.

It will list down the details in the Error List Window as shown below.

For Visual Studio Code :

For Visual Studio Code, after installing the SARIF Viewer, simply open the file

Below is how the result is displayed in the UI inside Visual studio code.

Hope it helps..

Using the PowerApps checker PowerShell Module to validate the solution

Using PowerApps Checker PowerShell Module we can perform the solution check functionality from outside the PowerApps Maker Portal. This can be useful for automated build and release pipelines. Apart from that some of the notable capabilities of the module include

Support for both managed and unmanaged solution.
Support for On-Premise.
Support for more than one solution at a time.

To get started à

Open the PowerShell (as administrator) and install the module

install-module Microsoft.PowerApps.Checker.Powershell

Next, we need to register an Azure Active Directory application in a tenant with PowerApps or Dynamics 365 licensing, even if it is on-premise environment (solution) against which we want to run it.

https://portal.azure.com

Click on New registration to register a new application

Provide the below details

Redirect URI

Type: Public client (mobile & desktop)
Redirect URI: urn:ietf:wg:oauth:2.0:oob

Copy the values of Application id and Directory (tenant) Id which we will use later and click on View API Permission to give the required permission to the app.

Click on Add a permission (we’d see Sign and read user profile added by default)

API level permissions to the PowerApps-Advisor first party Microsoft AAD application

Application permissions to Analysis.All

Permissions à

PowerApps solution checker uses Solution checker rule set. Here we are getting all the rulesets available passing our tenant’s id.

$rulesets = Get-PowerAppsCheckerRulesets -TenantId ‘290055c6-7eb1-4ec4-93e6-81f053d13f76’

We wil be using Solution Checker rule set here.

$rulesetToUse = $rulesets | where Name -EQ ‘Solution Checker’

Now let us run it against the Solution Zip file as shown below

$analyzeResult = Invoke-PowerAppsChecker –ClientApplicationId ‘48131848-3b81-44f7-a999-d8362b391f25’ –TenantId ‘290055c6-7eb1-4ec4-93e6-81f053d13f76’ –Ruleset $rulesetToUse –FileUnderAnalysis “C:\PowerApps\Test_1_0_0_1_managed.zip” –Output “C:\PowerApps\Result” -Verbose

Give the required consent

We can see the results download at the path specified

Result is in JSON format

IssueSummary to get the quick overview

Get all the details here

https://docs.microsoft.com/en-in/powershell/powerapps/overview?view=pa-ps-latest

Hope it helps..

Using PowerApps Solution Checker from the PowerApps maker portal

The PowerApps Solution Checker feature released for general availability on May 2019, can be used to perform static analysis of the Unmanaged solution for components like plugin, web resources, custom workflow activities and provide guidelines and recommendations around the issues found.

To get started à

https://make.powerapps.com/home

Select the Solutions in the left navigation pane and click on Install to install the Solution checker.

Click on GET IT NOW from the AppSource, specify the instance and the PowerApps Checker Solution will be installed in that Instance.

This will install the PowerApps Checker solution for the selected instance.

After the installation is done, we’d see the Solution checker menu enabled for the unmanaged solution.

Click on Run to run the test

We can see the results in the portal and can download the same as shown below.

Result of running it against another solution in which we are still using Xrm.Page object model à

The results will be available in both Excel and CSV format on the download

csv à

Excel will include a report as wellà

In the next post, we will see how to use the PowerApps Checker PowerShell Module to validate the solutions.

https://nishantrana.me/2019/07/12/using-the-powerapps-checker-powershell-module-to-validate-the-solution/

Hope it helps..

How to – Add Style to Custom Component in PowerApps Component Framework

Kindly refer the previous post, here we will be adding style to the component created in the post.

https://nishantrana.me/2019/06/06/step-by-step-create-a-very-simple-powerapps-custom-component-to-show-the-guid-of-the-record/

Let us continue with our previous sample component and try adding style to it.

Open ControlManfiest.Input.xml and specify the CSS file to be referred.

Uncomment the CSS tag in the manifest and create a new folder named CSS and place the CSS file there.

Edit the index.ts file and add the class to the label

Edit the CSS file

Edit the version number in case of updating the existing control in ControlManifest.Input.xml

Followed by the build command
npm run build

After the successful build, we can see the CSS added in the out folder for the component

Run the MSBuild command to generate the new solution zip files

Import the managed solution.
Open any of the existing contact records, we can see the style is applied to the control.

Hope it helps..

Step by Step – Create a very simple PowerApps Custom Component to show the GUID of the record

Update – use context instead of Xrm.Page

https://nishantrana.me/2019/10/22/using-pcf-custom-control-builder-xrmtoolbox-plugin-to-update-existing-control-in-dynamics-365-powerapps/

Also,

https://nishantrana.me/2020/01/20/best-resources-to-start-with-power-apps-code-component-pcf/

Go through below articles to get a better understanding

Below is the quick step by step guide to get started (sort of Hello World example)

Install NPM (that comes with Node.js)

https://nodejs.org/en/

Install Microsoft PowerApps Command Line Interface CLI

http://download.microsoft.com/download/D/B/E/DBE69906-B4DA-471C-8960-092AB955C681/powerapps-cli-0.1.51.msi

Install Visual Studio 2017 or later or Download .NET Core 2.2 along with Visual Studio Code.
Create the new folder for the project, and in Developer Command Prompt for VS 2017 navigate to the folder and run the below command to create a new component project

pac pcf init

– -namespace <namespace for the component>

– -name <name of the component>

– -template <component type>

It adds the following files in the folder.

Next run npm install command to install the project dependencies.

Open the ControlManifest.Input.xml file created inside the folder created with the control’s name.

Here we have opened it in Visual Studio Code, for this simple example purpose let us not change the default values.
Open the index.ts which wherein we’d be writing code for our custom control

Add the following line of code to add a label control that will display that GUID of the record.

Run npm run build command to build the control

To test the control run npm start command

*Use ctrl + c è to terminate the job.

Create a new folder to hold the solution

Run the below command to define the publisher name and prefix and initialize the solution files creation

pac solution init – -publisherName [publisher name] – -customizationPrefix [publisher prefix]

Run the below command to add reference to our custom control in the solution

pac solution add-reference – -path [path to pcfproj file]

i.e. reference of the below path.

This creates the file with extension cdsproj

To generate Zip File run the below command in the Developer Command Prompt for Visual Studio 2017
- MSBUILD /t:restore
- MSBUILD

This adds the Solution zip in the bin Debug folder.

To get both managed and unmanaged solution, update the cdsproj file

We can see both managed and unmanaged solution created.

Import the solution in Dynamics 365 CE and open any of the entity’s form. Here we have created a new text field named GUID in the Contact form and have set our custom control for that field.