Enhanced email for timeline in Dynamics 365 – 2020 release wave 2

With 2020 release wave 1, we had seen a couple of enhancements in Email experience


now this has been extended to Email within the Timeline section

Enable early access to 2020 release wave 2

Navigate to App Settings in Sales Hub, and click Manage for Enhanced email for timeline

Enable it and save.

Let us now navigate to one of the contact records and try creating a new email from its Timeline control

There we can now compose email in a pop-up and non-blocking window within the context of the record.

We can now work on a maximum of 3 active draft emails at a time.

The same rich edit experience which includes Drag and Drop / Copy and paste of the images is available.

In short, all the email enhancements that were added as part of Release 2020 Wave 1 is now available from within the Timeline control for email, making it a consistent experience for the users.

Hope it helps..

Enable early access 2020 release wave 2 – Dynamics 365

Finally, now we have the opportunity to opt-in for early access to release wave 2, to validate the new features in a non-production environment.

The features will be generally available on October 1, 2020.

Get all the details on the key dates and FAQ here


To opt-in

  • Log in to the Admin Portal


  • Select and open the environment to upgrade

  • Click on Manage in the Updates section and click Update Now

  • The upgrade process will start

  • Retry in case if any of the application updates fails using the Retry button, for us Dynamics 365 Core service had failed.
  • After a successful upgrade, the upgraded instance will show the 2020 release wave 2 enabled.

Hope it helps..

Show and hide the Dynamics 365 – custom app

To show and hide the Dynamics 365 – custom app from users other than having a system administrator role, we can use the below option

Navigate to Settings – Apps

and specify either Hide / Show for all roles.

For the end-users, it will hide the app

App not listed for the user.

Users can still access the app through URL.

The same settings can be applied from the General tab of System Settings

For Dynamics 365 On-Premise, we have a similar option in the General tab of System Settings

Hope it helps..

Notes on Claims-based Identify for Windows


I was recently reading about claims-based identity, noted down few important points

How Identity works inside the organization

The user enters his username and password to login to the domain. Now to access any application in the domain, the user gets the Kerberos ticket for the application from the AD. The ticket contains basic user information and is digitally signed by AD. The user provides this detail to the application, which checks the signature and makes sure it is issued by AD. Application, as it trusts the AD, uses the information in the ticket to perform the corresponding action.

The above authentication works well within an organization boundary, how about if a user wants to access an application from the internet, or belongs to a different domain, to address this we have claims-based authentication, which uses token.

A Token or security token is a set of bytes that expresses information about an entity e.g. a user. Token consists of claims and each claim contain some information about the entity. Token also has a digital signature.

The token is created/issued by STS – secure token service, which is commonly provided by an identity provider.

To get a token, the user will request a token from STS, which will usually ask for the user to provide username and password to authenticate and on successful authentication gets information about the user from the Account / Attribute Store like Active Directory to construct the claims in the token and sends the token back to the user after digitally signing it.

The user submits this token to the application he wants to access. The application uses the identity library to verify the signature of the token and also checks for whether the STS is trusted or not and then can use the claims in the token to define subsequent action that users can perform within the application.

Without claim-based identity, an application either has to authenticates users itself or rely on local 3rd parties to do that and it only gets only simple information directly from the user like the user’s name.

With claims-based identity, application see just see the token, they only need to decide whether they trust this STS, and application gets the exact information it needs, the STS puts it in the token as claims.

A claim can be used to identify the user, convey group membership, grant or deny access to specific methods, put constraints like purchasing limit, etc.

Through claims-based authentication, we can have an application that trusts multiple identity providers e.g. Google, Microsoft, Facebook etc. at the same time.

Microsoft Identity Provider
Identity Provider Federation Provider Identity Library
Cloud Windows Azure Active Directory Windows Azure Active Directory Windows Identity Foundation
On-Premise Windows Server Active Directory with ADFS. Windows Server Active Directory with ADFS Windows Identity Foundation

Windows Server Active Directory Domain Services

  • Provides Identity services for an organization.
  • Relies on Kerberos inside an organization.
  • The application can use LDAP to access the data it contains.

Active Directory Federation Services –

  • Provides an STS for claims-based identity.
  • Supports SAML Security Assertion Mark-up Language and other protocols.

Windows Azure Active Directory –

  • Identity and federation provider STS in the public cloud.
  • Applications can use the Graph API to access the data it contains

Window Identity Foundation is a standard library incorporated in .NET Framework 4.5 and above to work with claims-based authentication. We can build our STS using WIF.

  • Accessing an enterprise application – On-premise (Claims-based Identity)

  • Accessing an enterprise application – Internet (Claims-based Identity)

Check out the white paper / Channel 9 session / Pluralsight by David Chappell course to understand it in-depth




Hope it helps..

Adv Hands On Lab 5: Embedding PowerApps into Power BI

Step by step guide for embedding PowerApps within Power BI.

Key points to consider – https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/powerapps-custom-visual#limitations-of-the-power-apps-visual



Power BI Dashboard

In this lab, you will create a Power BI dashboard with an embedded PowerApp. The final product will look like the image below.

Exercise 1: Build Power BI Report

High level tasks

    Task 1: Connect to PowerBI and enable sample data. Build PowerBI report

    Task 2: Import PowerApp visual for use in report

Task 1: Build Report

In this task, you will build the Power BI Report.

  1. Navigate to https://powerbi.microsoft.com and click Sign in.
  2. At the bottom of the left navigation, click Get Data
  3. Select Samples.

  1. Select the Retail Analysis Sample.

  1. Connect.

  1. Your sample dataset will take a moment to load.

  1. Expand My Workspace and click to on the Retail Analysis Sample under the Datasets. If you have completed the prior steps and do not see this sample, refresh your browser.

  1. Go to the Fields pane, expand the Store table, and select the

View original post 924 more words

RetrieveTotalRecordCount function to get the total number of records in Dynamics 365

Using RetrieveTotalRecordCount Function we can get the total number of records for an entity (works for more than 50000 records)

For e.g.





Hope it helps..

SLA Changes in Dynamics 365/Power Apps

Prashant Kumar Maurya

Microsoft has made some changes in SLA design; here I am going to share about the differences

  1. SLA Type option standard has been removed, earlier user has option to choose (as shown in below image)

  2. Earlier there were 2 entities now there are 3 entities to configure a new SLA
    1. Earlier
      1. SLA
      2. SLA Item
    2. Now
      1. SLA
      2. SLA Item
      3. SLAKPI
  3. Earlier only one SLA can be applied now you can use multiple SLAs. This is a much-needed feature, in our recent implementation we need to have 5 SLAs on Work Order entity and to chieve that we need to implement a child entity on work order and create 5 records in that to track 5 different SLAs.

  4. To manage SLA settings, you can navigate to “Customer Service Hub” application and then navigate to “Service Configuration Setting”, there you can find below settings
    1. You can disable SLA on an entity which is…

View original post 147 more words

Notes on Adobe Campaign v6 – Extend and Customize

Continuing our previous posts, where we looked at Campaign planning, segmentation, deliveries, and running a campaign. Here we will look at some of the ways we can extend and customize Adobe Campaign V6.

We can use the Explorer option within the client console to view all the content within the Adobe Campaign instance.

Explorer renders the content in a tree structure as different folders as shown below.

The Operator within Access Management here specifies a user within the Adobe Campaign. Similarly, Operator Groups specifies the user groups.

We can specify access rights for an operator.

Navigate to the Access rights section for an operator and add appropriate rights.

The below screen shows all the different Access rights assigned to the operator named Test Account.

For each folder, we can specify operators or groups and the rights they can have on it.

There are 3 different types of workflows.

When it comes to adding Recipients it can be done manually as shown below by using the Create option, from the Recipients inside Profile and targets tab.

We can also import the data, that uses the import
template using the Import wizard. The import option also allows for how to treat duplicate data.

Similar to recipients, we can create our custom XML based data schema.

Below are the different options available while creating a new data schema.

We can also create custom forms in Adobe Campaign.

Below are 2 different types of (SOAP) APIs that we have in Adobe Campaign.

Check out the below Pluralsight training to learn in-depth

Extend and Customize Adobe Campaign v6

Hope it helps..

The Nigel Frank International Salary Survey 2020/21 for Microsoft Dynamics 365

The latest edition of Nigel Frank International’s Microsoft Dynamics salary survey is now live!

This will be their 12th annual report published, and has proven to be an invaluable resource to myself and my peers over the years.

I had the pleasure of contributing a foreword to the report, which set the scene in terms of where the Dynamics 365 ecosystem is now, what the future holds, and my own career journey. I can say with certainty that the ecosystem has been, and will continue to be, altered dramatically due to the Covid-19 crisis, as is the same with the technology sector as a whole.

The report uncovers a wealth of changing sentiments, along with work benefits, diversity statistics, the importance of certifications, and of course average salaries to name just a few topics covered. After reading through the results, here are my 5 main takeaways:

  • Certifications are growing in importance

The crisis has resulted in a huge increase of professionals upskilling; this is due to a combination of increased free time and job losses. Certifications are the best way to beat the competition in this increasingly difficult environment according to 61% of professionals surveyed, who believe certifications give you the edge in the job market. This along with the fact that getting certified can increase your salary by up to a reported 22% makes the decision whether to get certified or not an easy one. This was echoed by 80% of respondents who agreed Dynamics certifications were important towards increasing earning potential. Now is the time to upskill and safeguard your career!

  • The rise of working from home

The most obvious impact of Covid-19 on our working lives has been the shift from office to remote. The increase in related benefits offered such as a company laptop (73%) has followed, with 60% of respondents being offered homeworking. It will be interesting to see if this continues as restrictions across the world are beginning to ease, but it certainly seems the pandemic has changed our way of working forever. A company laptop and flexible/ remote working options have continuously been the most desired benefits when looking at past editions of the survey, so if this continues, job satisfaction will surely be boosted within the Dynamics workforce.

  • Equal rights are being championed

69% of respondents see their employers as being equal rights champions, which is hugely positive. Obviously, there is some way to go to reach the remaining 31%, however this signals change for the better across the industry. This along with 61% of employers promoting racial and ethnic diversity, and 56% hiring and retaining mature employees, is a resounding success. I hope this will continue and grow across the tech sector as a whole.

  • Increasing workload for partners

51% of employees working for Dynamics partners have seen their workload increase over the last year, and this was prior to the effects of the Coronavirus. This is a keen reflection of the digital skills gap, which will only be widening with the increased demand on cloud and digital in terms of keeping businesses and economies functioning. It is crucial that more people are encouraged into the tech sector in order to relieve the burden from these existing Dynamics professionals. This will be sure to further boost diversity within the ecosystem also.

  • Increased adoption of Dynamics 365

Since its release in November 2019, there has been an increase in take up from both new customers and existing users. 41% of end users, an 5% increase on last year’s result, are using Dynamics 365, with a further 19% expecting to use it in the future. The move to the cloud has been instrumental to this increase, and Dynamics 365 only looks to keep building momentum and customer base.

If you’d like to read the full report, and find out the average salary for your role and location, please do take a look here: https://www.nigelfrank.com/microsoft-dynamics-salary-survey/

Hope it helps..

ID3242: The security token could not be authenticated or authorized in Dynamics 365

We recently got this error in our web application while trying to fetch some records from one for CRM On-premise organization.

This error was because we had recently configured IFD for that CRM Server.

We had around 6 organizations in that particular deployment and because of security reasons, we didn’t use the wildcard SSL certificate and had a single certificate with multiple subject alternative names (SAN Certificate), and this organization was not part in it.

Fortunately, it wasn’t the case in our production environment and we had this organization part of the SAN Certificate used for IFD configuration there.

So as a quick and temporary fix, as we just wanted to test a couple of methods, we disabled the Claims Based Authentication / IFD from the deployment manager for that short period.

Hope it helps..