Apply SLA choosing the SLA in the SLA lookup field for the SLA Enabled Entities in Dynamics 365 CE

One of the enhancements that came in SLA (CRM 2016 Update 1), which I feel has got unnoticed by few, is choosing the SLA manually using the SLA lookup field.

As we all know SLA comes already enabled for Case Entity and can be enabled for the below entities

Account, Contact, Order, Invoice, Quote, Opportunity, Lead, Activity Entities.

Basically, the above entities have SLA lookup field already created for them.

We can also Enable SLA for custom entities and activities, which will create the SLA lookup field in it.

Add the field on the form and select the appropriate SLA, and that selected SLA will be applied to that record.

It saves us from defining multiple SLA Items for an SLA to be applied as DEFAULT or to use the entitlements to achieve the same.

Hope it helps..


ClickDimensions Features (Pros and Cons) and QuickStart guide

Word Version :!As1evjwQ4RIjjZRve-ZmrICdtmZoaA?e=KVDUDB

Pros of using ClickDimensions with Microsoft Dynamics CRM \ 365

Easy to set up and configure. ClickDimensions will provide a solution file which needs to be imported to the Dynamics CRM Web Application. It doesn’t require any setup files or any other infrastructure to be configured as it will be using the existing CRM Infrastructure.

Below we can see the ClickDimensions installed as Solution on top of existing Dynamics CRM instance. The solution import is followed by some basic configuration and we are up and running in no time.

It is the only tool available in the market that is natively embedded and exclusively built for Microsoft Dynamics CRM. So, the Microsoft Dynamics CRM Users will not have to switch between separate applications for the marketing needs and can use their existing Dynamics CRM skills for their marketing needs. It basically adds the required Group, Area and Subarea within CRM Web Application’s SiteMap as shown below.

As it is natively embedded with CRM, it has direct access to all the information and the data to be targeted for marketing like lead, contact, accounts and marketing lists that reside within CRM. In case of any other marketing tool, we’d have a Dynamics CRM Connector that needs to configured to sync the same data periodically and maintained at two different places one inside Dynamics CRM and other the marketing tool.

Relatively cheaper and cost-effective than other marketing tools available in the market Marketo, HubSpot, Pardot, etc.

Below are some of the prominent features provided by ClickDimensions for marketing needs

Email Marketing

The Email Marketing provides features specific to sending emails (Newsletters, Special offers, Instructions, etc.) to customers along with insights and statistics on how the customers are interacting with the emails.

Marketing List

To send bulk email, we would need to create a marketing list (static or dynamic). Marketing list can be used to target Lead, Contact or Account records inside Dynamics CRM.

Below is a sample Static Marketing List in Dynamics CRM

Clicking on the Manager Members button in the ribbon menu allows adding members to the marketing list.

Advanced Find option within Manage Members dialog box let us define the criteria for the members to be targeted as part of the marketing list for e.g. contact having age greater than 30.

In the case of Dynamic Marketing List, instead of actual members (records), query or criteria is saved in the marketing list and the marketing list members get updated automatically based on the query specified.

Email Templates

To create an email template in Dynamics CRM, navigate to ClickDimensions à Email Templates. Email Templates are used to design the Emails to be sent to the customer or clients. Email Templates can be reused or cloned to update some of the content to be sent to the recipients.

ClickDimensions provide different type of editors for designing Email Template as shown below à

  • The Drag and Drop editor allows creating email templates easily through dragging different types of content into different sections of the editor and editing the style and content of each cell and the entire email.

  • The Block Editor allows to easily create the templates by customising a built-in layout with a What You See is What You Get Editor.

  • The Free Style Editor is a little more advanced and allows the use of HTML with a What You See is What You Get Editor. If we already have email layouts designed, we will want to choose Free Style and upload our layout.

  • Custom HTML has very few buttons and is strictly HTML; there is no Design type of view. Use Custom HTML if you have created the template outside of ClickDimensions and don’t want to make any changes or additions, or if you know HTML well enough.

Email Template entity also provides a field called Text Version which allows you to specify the Text Version of the email so that anyone who cannot or wishes not to receive HTML in emails can still read the email.

Email Sends

Email Sends are the records using which the Email Templates created are attached to the marketing list and emails are sent out to the members of the marketing list associated.

To create an Email Send record, navigate to ClickDimensions à Emails

Click on New button to create the Email Send as shown below.

Let us go through each of the section and corresponding fields of the Email Send record.

The Status field will have the following values Draft, Pending, Sent, Error Recovery and Recovery Stopped, which shows the current status of the Email Send record. It will be Draft status, to begin with, and will be changed to Pending when being sent and Sent when sent from the system. User can click on Refresh Status to check the status instead of reloading the form.

Either an existing Email Template (optional field) can be associated or a new email template can be created for the Email Send. The existing Email Template associated can be further modified in the editor window in the Email Send. This will not update the original email template.

  • Subject is the mandatory field and specifies the subject for the email e.g. “Tomato Gardens”
  • Preheader will be the third line of text appearing in the message in the inbox for e.g. “See what’s new with us!”

  • Campaign field can be used to associate any campaign with the Email Send. The email sent records created for each of the members of the marketing list will then be associated with this campaign selected.

From Section of Email Send

  • When an Email Send is sent out while From Record Owner is set to Yes, the From Name and From Email values for each individual recipient will dynamically be set to the name and email address listed on the CRM User record of the Lead or Contact’s record owner.
  • If From Record Owner is set to No, every recipient will see the values in From Name and From Email. When From Record Owner is set to Yes, none of the recipients will see the values listed in the From Name and From Email fields on the Email Send unless the name and/or email address are missing from the Owner’s record. In this case, the values listed in From Name and From Email are used as back-up values.
  • From User field can be used to select any of the CRM users in the system. This will also auto-populate From Name and From Email field’s value from the selected user record.
  • Reply to email address field can be used to specify any email address if we do not want replies to be sent to From Email field.

Delivery section of Email Send

To schedule the delivery of the emails, the Send Immediately field can be set as No and Send On field can be used to specify the date and time as shown below.

Test Emails (Semicolon Separated) field can be used to specify the test email address (by clicking the Test button in the ribbon menu of Email Send form) before sending the emails.

Recipients Section of Email Send

Recipients section allows us to specify either Marketing Lists or individual contacts, leads or accounts record to which email needs to be sent as shown below.

Suppressed Marketing Lists section of Email Send

Suppressed Marketing Lists allows us to select one or more marketing list to exclude from Email Send.

Optional Advanced Settings Section of Email Send

  • Email Address Field specifies which field of contact, lead and account to be used for sending an email. By default, it uses emailaddress1 field.
  • Email CNAME – To brand the links differently than the default Email CNAME.
  • Add Google Analytics Campaign Tracking – If a campaign is associated with the Email Send then Google Analytics can be associated to it using this option.
  • Track Email Events – Indicates whether Opens and Clicks are recorded for Email Send.

Once all the required values are specified for the Email Send record, save it and click on SEND button to send the Emails.

Email statistics for Email Send

Once the email is successfully sent out, click on EMAIL STATISTICS button on the Email Send to get the email statistics.

Different tabs and details provided in Email Statistics à


Email Clients:


Click Reports:


Heat Map:

Marketing Channel – SMS

ClickDimensions supports sending text messages both in bulk and to individuals (Leads, Contact, and Account) using SMS Provider. Currently, it supports below three different SMS Providers.

  • Twilio
  • MessageNet
  • BulkSMS

The account or subscription for the above SMS providers needs to be bought separately and need to be configured in ClickDimensions.

Navigate to ClickDimensionsà
Bulk Text Messages

Click on New to create a new Bulk Text Message record

Bulk Text Message Section Overview

  • Subject: This will be the subject of the Text Message
  • Campaign: To associate the record with a campaign.
  • Send Immediately: Specify whether to send the message immediately. Set it to No and specify a date in Send on the field to schedule it.
  • Send On: The date on which the messages should be sent when scheduled.
  • Status Reason: The status of the record.
  • Recipients: Add the marketing list to which text message is to be sent.

Message Content area is where we can compose the text message.

The dynamic drop down allows us to pull the information from the respective lead/contact/account records added in the marketing list.

Once the message is composed, click on Send to send the Bulk Text Message.

To send individual SMS, open any existing lead, contact or account record and click on other activities and create the Text Message record with appropriate details and click on Send.

SMS Statistics

Open up the sent Bulk Text Message, it will have a section name Statistics that shows the total messages that have been attempted to send.

Click on Closed Activities menu for the sent Bulk Text Message record to see that individual SMS statistics

SMS Replies

SMS Provider i.e. either Twilio and BulkSMS can be configured to allow SMS recipients to respond to the SMS Messages. These responses get associated with the respective lead or contact records in CRM.

To see replies, go to Activities and select Received View for Text Message entity.

SMS Unsubscribes

The SMS recipients can reply with one of the following responses to be unsubscribed from SMS.

  • unsubscribe
  • stop
  • remove
  • 688
  • *688

This updates the field Allow Text Messages in Lead/Contact/Account record to “No”

Marketing Channel – Events

Events capabilities of ClickDimensions allows us to create Event Records and Event Participant Records which will be associated with existing lead or contacts records if matching email address exists if no matching email address is found lead or contact records are created in CRM based on the configuration done.

Below are the connectors supported by ClickDimensions for Events

  • GoToWebinar
  • WebEx
  • Eventbrite
  • Cvent

Once the connector is configured for any of the above Events Provider from ClickDimensions à Settings à Connectors section,

Navigate to ClickDimensions à Events to view all the events generated.

Sample Event Record

Navigate to ClickDimensions à
Event Participants to view all the Event Participants records.

Sample Event Participants

Note: Event and Event Participant records can also be created manually if connectors are not used.

Marketing Channel – Social

Social Marketing feature allows CRM Users to create, schedule and publish social posts and to track the interactions people are having with theses posts from within Dynamics CRM.

The different connectors supported are

  • Facebook – Facebook Page and Facebook Group are supported.
  • LinkedIn – LinkedIn Profile and LinkedIn Company are supported.
  • Twitter – Twitter Profile.
  • Instagram

To create social posts, navigate to ClickDimensions à Social Posts

Click on New to create a new Social Post record.

Sample Social Post

Click on Create Post to create, schedule and publish the Social Post à

Sample Post:

Once a social post has been published, the Social Post record will show the details of the Social Post along with the Social Clicks information as shown below.

The Page View record will show the details of the clicks on links from the published social post.

Navigate to ClickDimensions à Page Views

Sample Page View

Web Content – Forms

ClickDimensions allows CRM users to create Forms that will allow visitors to submit information like name, email address, phone number, country, etc. which is then stored in CRM. These forms can be embedded in the landing page or on the website and this information can be associated with the lead or contact record in CRM.

There are 2 ways of creating Forms in ClickDimensions

Form Builder and Form Capture

Using Form Builder, we can create the form from scratch whereas Form Capture uses an existing HTML for the existing web site of the company.

The first step is to create Form Fields.

Navigate to ClickDimensions à Form Fields and click on New

Different type of fields that can be created

The new form field needs to be mapped with existing fields in Lead and Contact as shown below.

Navigate to ClickDimensions à Web Content and create a new Web Content of type Form for adding the Form Fields and designing the form using Form Builder.

Click on Design to open the form designer and drag and drop the forms fields in the Form Designer canvas to design the form

Click on Actions to define the action to be performed after submission of the form.

Click on Embed which will list down various options of embedding the form.

We can also use Form
Capture to use existing HTML in the website for creating our form. Before we can use the existing web page for Form Capture we need to make sure the page is accessible over the internet, the ClickDimensions tracking script must be installed and working on the page.

The Form Fields records should be already created and associated to Form Capture fields and are being referred with their Form Field Id value in the name property inside HTML as shown below.

Navigate to ClickDimensions à Form Capture and click on New to create a new Form Capture

The Form Action URL will be used in the action URL in the HTML Page.

Go to related records for the Form Capture record created and create a new Form Capture field

Specify the Form Field to be used in Form Capture and save the record. Repeat the same steps for additional fields.

Web Content – Surveys

ClickDimensions provide the Survey feature for getting user’s feedback. This can be embedded in landing pages or web site and the answers provided can be associated with lead and contact records in Dynamics CRM.

To get started we need to first create the Survey Questions. Navigate to ClickDimensions à Survey Questions and click on New

Below is the different type of Survey Questions that can be created.

Once we have created all the Survey Questions, we need to create Web Content of type Survey. Navigate to ClickDimensions à Web Content and click on New.

Click on Design button on ribbon menu to Design the survey.

Below are the different Survey Components that can be added in Survey

After we are done with designing the Survey, we can select Actions to define the action to be taken once the Survey is submitted by the user as shown below.

Once we are ready to Publish the Survey, we can click on Embed and select the appropriate option.

Navigate to Posted Survey record to check the Survey Statistics

Web Content – Landing Pages

Landing Pages are stand-alone pages for any advertisement, newsletter, distribute coupon codes, etc. The landing pages can embed Survey and Forms in them.

To get started, Navigate to ClickDimensions à Web Content and create on New to create the new Web Content record of Type as Landing Page.

Landing Page supports 2 different type of editors – Free Style and Block Editor.

Click on Design to open the designer.

The Free Style editor

The Block editor

Once we are done with designing and are ready to Publish the Landing Page, we can click on Embed on Designer and select the appropriate options

To link the landing page with the Campaign, copy the Campaign Code from the campaign record and place the code inside the Landing Page or through the Campaign field in the Web Content record.

Page View related record of Campaign will have the details of all the visits to the Landing Page.

Campaign Automation

Campaign Automation feature allows the user to set up the dynamic path that a campaign will follow using Triggers and Actions.

Navigate to ClickDimensions à
Campaign Automation and click on New to create the new Campaign Automation record.

Save the record and click on Open Builder to create a new Campaign Automation Builder which provides the canvas for defining and building the Campaign Automation.

Campaign Builder: On the right side we have Triggers, Actions, Timers and Series which can be dragged onto the canvas.

Below link and the pdf list down some of the examples of Campaign Automation

Lead Scoring

ClickDimensions provides Lead Scoring capability for the Lead, Contact and Anonymous Visitors (custom Click Dimension entity). Here scoring specifies the interest level of the individual which is calculated based on email clicks, web form submissions, page view, link clicks, etc.

Navigate to ClickDimensions à
Anonymous Visitors

The score field shows the Total Score for the Anonymous Visitor

For Contact and Lead, the value is available is the Total Score field on the form.

The Score values can be modified from ClickDimension à ClickDimension Settings à Score Settings

Cons of using ClickDimension with Microsoft Dynamics CRM

The SMS marketing feature is limited and doesn’t provide a details statistic and reports similar to Email marketing. Currently supports Twillio, MessageNet and BulkSMS connector which comes with additional cost. If we are planning to use some other Vendor instead of the above 3, then custom SMS integration needs to be built in Dynamics CRM using the Software Development Kit provided by Microsoft.

There are certain limitations with regards to what fields can be dynamically accessed inside ClickDimensions for Email and SMS marketing.

  • For Emails – It can pull data from LeadContactAccountOwner (User), EmailSend entity and those entities that have an n-1 relationship to them. And that also only up to one level.
  • For SMS – It can pull data from LeadContactAccountOwner (User) entity and those entities that have an n-1 relationship to them. And that also only up to one level

The workaround to get data from any other entities is to create the custom fields in the Owner, Lead, Contact, Account, and EmailSend entity and populate them which requires customization.

Tightly integrated with Microsoft Dynamics CRM, so if we want to run a campaign for Customers that exist in other systems/applications, we need to push/sync that information inside CRM first.

Doesn’t support Inbound Marketing (blogging, webinar, podcast, etc.).

Doesn’t have Predictive Analytics or AI features

Additonal Resources

Hope it helps..

Single Organization vs Multiple Organization (Single Instance vs Multiple Instance) key points to consider in Dynamics 365 CE (On-Premise)

The decision for going with single or multiple organisation should be made as early as possible because if the implementation grows, it will increase the complexity. For e.g., if we have Marketing already implemented for the marketing lob and now, we are planning to add Sales and Service, which would be difficult as it could require updating the existing implementation (plugins, workflows, BPF, Security Model, Business Unit structure, etc.) to cater for addition of new LOBs. If the implementation of the system is designed from the very beginning keeping different LOBs in mind, the complexities can be managed. Also, there is a possibility that a single instance which is serving different LOBs, needs to be separated to multiple instances later, this again will require additional efforts.

Below are some of the factors and pros and cons that we would need to consider before deciding on Single Organization vs Multiple Organization (Single Instance vs Multiple Instance).

Companies with Business units \ LOBs having a different set of customers and different
functional area with no need for

  • cross-business collaboration
  • sharing of data
  • unified or roll-up reporting
  • the same set of standardization

will benefit from Multiple Organization or Multiple Instance approaches.

The benefits of Multiple Organization or Multi-Instance are

Reduced complexity when it comes to the designing and implementation of the data model and security model.

Having less volume of data stored in the system could contribute to improved performance of the application.

Having a lesser number of customization (plugins/workflows/business rules etc.) without segregation logic for different LOBs could also contribute to improved performance.

Provides autonomy, so easy to implement new features/functionalities/3rd party applications without having to consider the impact of it for other business units.

Easy and efficient release management e.g. fast deployment, lesser downtime and do not have to be agreed upon for all the LOBs, less need of regression testing, etc. with fewer teams/functionality being impacted.

Fewer chances of exceeding organization limits for e.g. we have following limits in Dynamics 365 CE /CRM – 100 rollup attributes and each entity having 10 rollup attributes, 10 activated business process flow per entity, maximum number of entities that can have active SLAs is 7, maximum number of SLA KPIs allowed per entity is 5 etc.

System-level settings through Administration à System Settings could be easily governed, managed and defined for the single organization without affecting other LOBs for e.g. some of the settings like – Decimal Precision Point, Relevance Search or Categorized Search, Using legacy form rendering, Session Timeout, Audit settings, etc.

For Customerflexibility to have different implementation team (partners/vendors) working on separate organizations (administration, implementation, support, etc.)

Also, if there are any regulatory or compliance that has to be in place for one LOB it would adversely affect other LOBs in case of the single instance as essentially, they’d be sharing the same resources.

On the other hand, companies having Business Units with the need for coordination and sharing information/data having process standards, rollup reporting needs will benefit from a single organization or single instance approach.

Rollup and Unified reporting and cross-business unit collaboration can be achieved easily in case of a single organization as all their information would be residing in the same instance’s database without any need of User Interface Integration/ SQL Server Replication / Web Service Integration / Publish/subscribe pattern by plugin-ns.

Check out the whitepaper here

Most of the 3rd party applications in App Source like ClickDimensions supports only single instance, so different LOBs part of that same instance can share it, which will not be the case of multi-instance, as it would require separate licenses to be procured.

Required common functionalities would still need to build/deployed into multiple organization i.e. less reuse of configuration and code, which can be easily shared and standardized in case of singe organization.

No need for data replication or information (customer, contact, etc.) to be duplicated in all the instances in case of multi-instance.

For multi-instances in case of Online, there would be an additional cost associated with adding instance (sandbox and production).

Also, additional cost in case of multi-instance, for procuring any 3rd party application for each of the instance that needs it, increased integration/ replication cost.

For multi-organization in case of CRM On-Premise, there could be added infrastructure cost to support that many organizations.

Multi instance/organization can also plan to use the Hub and Spoke strategy. This would be recommended approach in case of independent but similar LOBs (e.g. located at different region/geography) i.e. replication.

Few important factors to be considered are as below

Ownership Cost – Who within the organization/enterprise is paying and owning the CRM System.

Does the organization have a Global Center of Excellence (CoE)?

There is no denying that having a single instance service multiple LOB(s) will have added complexity which will only grow with time as the implementation progresses (enhancements/ phases), does the organization has the plan or a roadmap clearly defined to handle it with all the stakeholders involved aligned with Enterprise strategy and architecture.

Please feel free to add your thoughts, suggestions and insights in comments.

Hope it helps ..

Getting entity record counts

RetrieveTotalRecordCountRequest to get the total record counts instead of navigating through pages 🙂

Dreaming in CRM, PowerApps & Flow

There are couple of ways to gets entity record counts: you could use XrmToolBox’s Record Counter Tool, or write the FetchXml to count the records as you navigate from one page to the next. But, if you just want to use the SDK here is a simple method: a new message called RetrieveTotalRecordCountRequest. Here is how to use it in C#:

Retrieve Record Count

Here is the same call in JavaScript:

Retrieve Record Count JS

Hope this is useful.


View original post

SSRS and Power BI comparison for Dynamics 365 CE Reporting


Was recently working on a comparison between using SSRS and/or Power BI for reporting for Microsoft Dynamics CRM, below are some of the points we came up

SSRS has always been Reporting Tool of choice for Microsoft Dynamics CRM and has been natively integrated with the application.

  • Microsoft Dynamics CRM offers Report Parameters for SSRS that are specific to CRM and can be used while writing custom reports using SSRS.
  • Microsoft Dynamics CRM provides CRM
    Pre-filtering feature using which user can use to create a context-sensitive report. Pre-filtering basically passes the specific record (or selected records) information on which report is to be run and renders the result after pulling the information from those record(s). These reports can be uploaded and run from inside the form or grid (list of records) or from the Reports Area within CRM.
  • Microsoft Dynamics CRM provides Filtered Views against which SSRS Report are written.  Filtered views conform to the Microsoft Dynamics CRM security model so the data shown in an SSRS report using a filtered view would only contain the data the users can view and has access in CRM
  • SSRS Reports adheres to Security Model of Dynamics CRM. They can viewable by the Organization or Individual. Individual reports can be shared with other users within the system through the Sharing feature.
  • SSRS is an ideal solution for something to be printed, for e.g. operation documents like invoices, work order, etc. as it gives fine-grained control over location as well as formatting of each of the report components/controls.
  • SSRS has support for more advanced printing features such as footers, headers, watermarks, and page numbers. We can easily configure the margins and layout of your report to get it exactly the way you want.
  • It is easy to extract data as well as export the SSRS report to a different format like word, excel, CSV, pdf, XML, etc.
  • Delivery reports in multiple formats automatically (Scheduling via Subscriptions).
  • There are some limitations for CRM Online reporting which has mostly to do with limitations of Fetch XML.

Interactivity and Data Exploration is where Power BI wins over SSRS à

  • For interactivity and data exploration we can use parameters, drill-through reports or action links, however, comparing this to Power BI, it is very limited, if we click on a visual, all of the other visuals automatically cross-highlight or cross-filter.
  • Advanced Visualisation support in Power BI.
  • Because of the limited interactivity, SSRS is not ideal for data exploration. We have limited options for slicing and dicing the data. SSRS makes more sense when you know what you want the end result to look like. If you to play around with the data, you are much better off with Power BI.
  • Mobile support is much better for Power BI.
  • Support a large number of data sources.

In short, both the tool can be used and can co-exist as they fulfil a different set of requirements.

Would appreciate if you could provide your thoughts in the comments and some additional points.

Hope it helps..

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


Hope it helps..

Using 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.

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.

  • Login to Azure Portal

  • 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\” –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

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 à

Sign in to PowerApps maker portal

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.

Hope it helps..

Fixed – Package Deployer (USD) not connecting to CRM Organization

Hi, while trying to set up USD in the Dynamics 365 Online environment

We were facing the issue with the USD’s Package Deployer, after login, it was showing the Organizations but on trying to connect to them, it was again taking back to the login screen.

This was because we were using below old version of the Package Deployer


To get it working as suggested by Microsoft we had to update the registry and add the following key – “SchUseStrongCrpto

This makes the .NET application, in our case, the older version of the Package Deployer to use TLS 1.2 required for connecting to Version 9.0 of Dynamics 365.

After making the registry change, we were able to move forward.

We will not be facing the same issue with newer version of USD

Hope it helps.