Tag: PowerPlatform

If you only understand the first and the last part of the title, you should click the button below to learn more about the “Power Apps Developer Plan” that includes a free Dataverse for developer (and for makers or course).

GOTO “Power Apps Developer Plan” page at Microsoft

Normally Power Platform administrators can create, edit and delete Dataverse environments through the “Power Platform Admin Center” (https://admin.powerplatform.microsoft.com/environments), but developer environments from the “Power Apps Community Plan” differ here.

They can only be created through the “Power Apps Developer Plan” page at Microsoft (button above)
Everyone with Microsoft work or school account can create one personal development environment per tenant
They can not be edited (update name or URL) or deleted through the portal

How to delete a developer environment

I found out, that Nick Doelman already has perfectly described, how to delete a Power App Community Plan environment with PowerShell. Inspired by his blog post, I remembered that there is a “Power Platform for Admins” Connector for Power Automate (and Logic Apps) and I checked it out for you.

Open the the Maker Portal (https://make.powerapps.com) and select the default environment of your tenant on the right side of the header menu. Only there the Flow will be later reusable, because you don’t delete it with the environment it exists in.
Create a new instant Cloud Flow and give it a name, for example “Reset DevEnvironment”
Add an input parameter to the trigger action that will receive the environment ID

Search for the “Power Platform for Admins” connector and select it. I got the best search result by typing “PowerApp”.

the power platform for administrators connector

Now scroll down and select the “Delete Environment” action.

delete a developer environment with power automate

Select “Enter Custom Value” as environment input for the action and choose the ID that comes from the trigger action

Save your Flow

Usage of the flow

Open the “Power Platform Admin Center” (https://admin.powerplatform.microsoft.com/environments) and copy the Environment ID

Now run the Flow and paste the Environment ID as parameter.

The flow run takes something between 30 and 120 seconds and ends with an 404 error, but at the end the environment has gone and you can create a new Power Apps Community Plan Environment again.

30.10.2021

Ben

Bulk active Flows from a solution

Posted in Power Automation, Dynamics 365, and Power Platform

Scenario

We start our projects with our best practice solution and add further value over time to that solution. We also try to let benefit existing customers from the innovations and optimizations that get implemented in the solution over time, since their project has started.
Knowing our goal, you can imagine our setup. A source instance in our tenant and several target instances at different customers.
On top, some customers receive manual, an unmanaged version of the solution and other customers receive a managed version with an Azure Pipeline.

Issue

Flows can only be turned on if the user turning them on has permissions to connections being referenced by the connection reference.
Marc Schweigert: https://gist.github.com/devkeydet/f31554566b2e53ddd8e7e1db4af555a6

This causes no issues when importing manually, but as we use Application User to connect the Azure Pipeline, this ends with all Flows in the solution turned off after solution import.

Solution – Bulk active Flows

One solution would be to create a PowerShell script in the Azure Pipeline that impersonate the owner of a connection reference (Source).
I decided to create a Power Automated based solution to bulk active Flows, with an Environment Variable that contains Flows that should not be enabled automatically.

Step by step

Step 1 – Environment Variable:
Create an Environment Variable of type JSON to store the Flows that should not be activated automatically. Doing this as an Environment Variable enables you to define this per instance.

To enable our Flow to find the right Flows by name, workflowid or workflowuniqueid, the structure should be:

{
  "Flow 1": "worklowid",
  "Flow 2": "workflowidunique"
}

Step 2: The Trigger of the Flow

A managed solution only get modified when you import an update of it. Therefore, this is my trigger, filtered on my solution.

The dataverse flow trigger on table 'Solutions'.

Step 3: Some vars and const

Step 4: Get the exclusion list

I needed to put it in a compose action. Working directly with the environment variable did not work for me.

Step 5: Get inactive Flows from the solution

Get the inactive Flows from the solution with a fetch to bulk active flows later.

I found the FetchXml in the Dynamics Community, it was an answer from Scott Durow where he helped someone. By that way, thank you, Scott, that inspired me to my solution.

<fetch>
  <entity name="workflow">
    <attribute name="category" />
    <attribute name="name" />
    <attribute name="statecode" />
    <attribute name="workflowidunique" />
    <filter>
      <condition attribute="category" operator="eq" value="5" />
      <condition attribute="statecode" operator="eq" value="0" />
    </filter>
    <link-entity name="solutioncomponent" from="objectid" to="workflowid">
      <link-entity name="solution" from="solutionid" to="solutionid">
        <filter>
          <condition attribute="uniquename" operator="eq" value=@{outputs('Solution')} />
        </filter>
      </link-entity>
    </link-entity>
  </entity>
</fetch>

Step 6: Loop over fetched Flows

Step 6.1 Check inside the loop if the current Flow is not excluded

Condition to excluded flows from the environment variable.

contains(string(outputs('Get_ExclusionList')), string(items('Loop_fetched_Processes_from_Solution')?['workflowid']))


contains(string(outputs('Get_ExclusionList')), string(items('Loop_fetched_Processes_from_Solution')?['workflowidunique']))


contains(string(outputs('Get_ExclusionList')), string(items('Loop_fetched_Processes_from_Solution')?['name']))

Step 6.1.1 Activate the current Flow in the TRUE path of the condition

Update the record in Dataverse to activate the flow.

Step 6.1.2 Log if an error happens after activating the current Flow

Click the three dots on the “Counter++” action and choose “Configure run after”.

Step 7: Check if an error occurred, after the loop is completed

Step 7.1 If an error occurred, get the URL of the CRM instance

I described how to get it in my post: Get CRM URL in Power Automate

Step 7.2 Send a notification

Let me a comment if you find this helpful or how you solved this or a similar problem.

17.06.2021

Ben

Best practices for ClickDimensions deployment

Posted in Dynamics 365, ClickDimensions, and Power Platform

1. Basics

ClickDimensions is only accessible and configurable through Dynamics 365 Customer Engagement. This is achieved through CRM records (forms, templates, emails, etc.) that are linked by their GUID and the CRM instance specific ClickDimensions account key to an ClickDimensions editor/designer that stores its content in the ClickDimensions cloud infrastructure on Azure.

Like Microsoft, ClickDimensions provides its customers sandboxes and additional production instances for their Dynamics 365 CE environment.
A sandbox instance is hereby fully functional and can send out an email blast to your CRM records like any production instance. It’s not a safe playground if your test environment is a copy of the productive data.

2. Deployment

After purchase, you register for a ClickDimensions cloud instance(s) with your CRM instance(s). Afterwards, you will receive an email with a download link for a Dynamics 365 solution for each of your registered ClickDimensions instances. Make sure not to mix up them with your CRM instances, because the ClickDimensions account key fix embedded in the ClickDimensions solution. The same applies later to updates.

Create a backup solution in Dynamics 365 save ribbon customizations on account, campaign, contact, lead, list, opportunity, team and systemuser. Add only the required entities with their metadata to keep the solution as clean as possible.

If you have Dynamics 365 CE instances that will have no ClickDimensions Instance – like a development environment, you can import any of the ClickDimenions solutions to have the same customizing for all Dynamics 365 instances

3. Customizing

The CRM parts of ClickDimensions can be customized like any other CRM elements. Avoid customizing of views and form sections, they could be overwritten during an update.

Don’t forget to publish the metadata to the ClickDimensions cloud if you created fields that should be accessible through ClickDimensions.

Processes that you build on top of ClickDimensions processes, will have no influence on the ClickDimensions cloud. A campaign automation instance that has a posted form as an entry point, will still run with the same contact from the start, even if you updated it on the posted form in CRM.

4. Transport

The ClickDimensions Export and Import let you transport Domains, Email Templates, Form Fields, Landing Pages and Survey Questions.

All other configuration records must be transported manually. I prefer the XrmToolBox – DataTransporter to create records across all CRM instances. Pay attention to only transport the fields that you can edit in CRM. Exclude the CRM GUID and any other ID/Key from ClickDimensions (except for redeployment).
Web content and campaign automations must be rebuilt manually.
Check also the linked web content in email templates to prevent submissions to wrong CRM instance.

Those of you who are willing to experiment can try to capture and modify the body of the web request that is submitted when you save a web content.

5. Updates

ClickDimensions has a 4-week release cycle.
In the Release Notes, you find detailed information of what has changed and if a solution update is required to receive new features or bug fixes.
Most of the changes take place on the server, and a solution update is recommended by ClickDimensions once a quarter.

I prefer the manual update of the ClickDimensions solution, because I can determine when the system changes.
As the release cycle is really short, I advise to download the solutions for all instances at once. Otherwise, it could happen that you download different versions. Don’t forget your backup solution and the import in your CRM instances without ClickDimensions the have the same customizing over all.

During the update, you have to choose the settings that are “not recommended” by Microsoft to overwrite the existing ClickDimensions customizations.

It makes sense again to have a backup solution in with ribbon customizations from account, campaign, contact, lead, list, opportunity, team, systemuser and additional customizations on ClickDimensions entities.

6. Redeployment

Make sure to have a ClickDimensions solution of the system that you overwrite and a backup of the ClickDimensions records with all attributes from that system.

The redeployed CRM instance will still try to connect to ClickDimensions environment of the source CRM.

Disable all the ClickDimensions plugins, the redeployed CRM instance will still try to connect to ClickDimensions environment of the source CRM and could delete your productive data in the ClickDimensions cloud.

Delete the copied ClickDimensions records from the redeployed system. Delete also the records in the “Execute Send” table through the advanced find.

To restore the ClickDimensions records, you can import the backup of these records, with all keys and the original GUID of the records.

Reconnect the CRM instance to the correct ClickDimensions cloud instance, by importing the ClickDimensions solution from the first redeployment step.
This will restore the account key, enable the plugins, and you are able again to create new records and open the restored records in the redeployed system.

03.06.2021

Ben

One Comment

Understand email statistics in ClickDimensions

Posted in ClickDimensions, Dynamics 365, and Power Platform

Email statistic calculation

If you’ve ever wonder why the count of your marketing lists members differs from the email statistic that ClickDimensions has sent, then the following list will help you to understand how ClickDimensions calculates the email delivery.

Email statistic report from ClickDimensions

+ LISTED RECIPIENTS
- + Recipients – leads, contacts and accounts that are connected to the ‘cdi_emailsend’ as recipient, directly or via marketing lists
- – Duplicate email addresses over the recipients
– EXCLUDED RECIPIENTS
- + Recipients without an email address
- + Email addresses that are already blocked
  - + Email addresses with a previous hard bounce
    - + DNS failures
    - + Generic Bounces: No RCPT
    - + Invalid Recipients
  - + Email addresses with 4 soft bounces within a 90-day period
  - + Email addresses that were blocked in a previous email
- + Recipients with unsubscribed email addresses
  - + Recipients ‘donotemail’ setting is ‘Do not allow’
  - + Recipients ‘donotbulkemail’ setting is ‘Do not allow’
  - + Recipients whose email address is listed in the ‘Unsubscribe’ records
  - + Recipients whose email address is opted-out from the related subscription list
  - + Recipients whose email address have no opt-in for the related subscription list (only in opt-in model)
- + Suppressed recipients
  - + Email addresses from leads, contacts and accounts that are connected to the ‘cdi_emailsend’ via a suppressed marketing list
= MESSAGES SENT
– BOUNCES
- + Hard bounces
  - + DNS Failures
  - + Generic Bounces: No RCPT
  - + Invalid Recipients
- + Soft bounces
= EMAILS DELIVERED

Queries for email statistic in D365CE

This list contains the OData 4.0 queries to collect all the data for email delivery and interactions for reporting purposes.

GET [Organization URI]/api/data/v9.1/

Excluded recipients
cdi_excludedemails?$filter=_cdi_emailsendid_value eq {ID}
Recipients without an email address
cdi_excludedemails?$filter=_cdi_emailsendid_value eq {ID} and cdi_reason eq 4
Recipients with already blocked email addresses
cdi_excludedemails?$filter=_cdi_emailsendid_value eq {ID} and cdi_reason eq 5
Recipients with unsubscribed email addresses
cdi_excludedemails?$filter=_cdi_emailsendid_value eq {ID} and (cdi_reason eq 1 or cdi_reason eq 7
Recipients that are connected via a suppressed marketinglist
cdi_excludedemails?$filter=_cdi_emailsendid_value eq {ID} and cdi_reason eq 6
Messages sent
cdi_sentemails?$filter=_cdi_emailsendid_value eq {ID}
Hard bounces
cdi_emailevents?$filter=_cdi_emailsendid_value eq {ID} and (cdi_type eq 10 or cdi_type eq 15 or cdi_type eq 9
Soft bounces
cdi_emailevents?$filter=_cdi_emailsendid_value eq {ID} and cdi_type eq 3
Emails delivered
cdi_sentemails?$filter=_cdi_emailsendid_value eq {ID} and cdi_bouncescount lt 1 and cdi_deliveriescount gt 0
Interactions
cdi_sentemails?$filter=_cdi_emailsendid_value eq {ID} and (cdi_clickscount gt 0 or cdi_openscount gt 0)
Unique opens
cdi_sentemails?$filter=_cdi_emailsendid_value eq {ID} and (cdi_openscount gt 0)
Total opens
cdi_emailevents?$filter=_cdi_emailsendid_value eq {ID} and cdi_type eq 2
Unique clicks
cdi_sentemails?$filter=_cdi_emailsendid_value eq {ID} and (cdi_clickscount gt 0)
Total clicks
cdi_emailevents?$filter=_cdi_emailsendid_value eq {ID} and cdi_type eq 4
Unsubscribes
cdi_emailevents?$filter=_cdi_emailsendid_value eq {ID} and cdi_type eq 6

Inferred opens

An inferred open is counted when a recipient clicks a link in an email or unsubscribes, but does not download the images (and also the tracking pixel) in the email.

The unique opens in the email statistics in Dynamics 365 CE do not include inferred opens.
The ClickDimensions email report includes the inferred opens in its unique opens count.

KPIs calculation from email statistic values

Basics for marketeers but maybe not for Dynamics 365 folks and of course it is also handy to have all in one place.

Bounce rate
Bounces / Message sent * 100
Soft bounce rate
Soft bounces / Message sent * 100
Hard bounce rate
Hard bounces / Message sent * 100
Delivery rate
Deliveries / Messages sent * 100
Interaction rate
Interactions / Messages sent * 100
Open rate
Unique opens / Messages sent * 100
Click rate
Unique clicks / Messages sent * 100
Unsubscribe rate
Unsubscribes / Messages sent * 100

25.03.2021

Ben

ClickDimensions Release Notes – All-In-One Edition

Posted in Dynamics 365, ClickDimensions, and Power Platform

ClickDimensions has a monthly release cycle with a yearly major release. Surely you can imagine that most of the customers don’t prefer the automatic update and of course nobody makes manually updates on a regular basis.
The result of this combination is that I get often the question from customers: “What has changed since our last update?”.

The release notes of ClickDimensions are public available as single articles, starting from Feb 2018 – v9. These article contain the changes for each single version.

Therefore, I started my own document that combines these releases notes articles, and I want to share it with you.

Features of my ClickDimensions Release Notes All-In-One Edition

Or in other words: “Benefits of bringing them in all together in an Excel file.”

Filter by date (EU release) or ClickDimensions version
Filter by ClickDimensions feature (Campaingautomation, Email, Analytics, etc.)
Filter by type (new features, improvements, changes and fixes)
Filter by update type (instant update or solution update required)
Search for a defect number
Versions that are not supported anymore are greyed out

Tag: PowerPlatform

How to delete a developer environment with Power Automate

How to delete a developer environment

Usage of the flow

Bulk active Flows from a solution

Scenario

Issue

Solution – Bulk active Flows

Step by step

Best practices for ClickDimensions deployment

Table of content

1. Basics

2. Deployment

3. Customizing

4. Transport

5. Updates

6. Redeployment

Understand email statistics in ClickDimensions

Email statistic calculation

Queries for email statistic in D365CE

Inferred opens

KPIs calculation from email statistic values

ClickDimensions Release Notes – All-In-One Edition

Features of my ClickDimensions Release Notes All-In-One Edition