Deprecation of Office365 authentication type and OrganizationServiceProxy class for connecting to Common Data Service

Recently came across this article from Microsoft. Please see the below link for further details.

https://docs.microsoft.com/en-us/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-common-data-service

Effective Feb 4, 2020, the WS-Trust authentication type that is used by custom clients to connect to Common Data Service is deprecated. This change affects applications that utilize Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy and Microsoft.Xrm.Tooling.Connector.CrmServiceClient classes for the authentication type of "Office365".

Important dates are the below

To allow for transition of customers and partner applications:

• Effective April 2021, we intend to retire this authentication protocol for all new environments.
  
• Effective April 2022, the authentication protocol will be retired for all new and existing environments.

Dynamics 365 Attachments Issue with Azure Blob

Attachment Management for Dynamics 365 Online using Azure blob storage. If you are not familiar with this solution here is the post.

https://crmdm.blogspot.com/2018/11/dynamics-365-attachments-in-azure-blob.html

Recently we noticed that some documents were showing as 0 KB in a lower environment. After some investigation it was found that the SAS token was expired. Attachment management solution is configured using SAS token. After fixing the SAS token all documents were displayed correctly. It's important to check the expiry of the SAS token

New API Limits for Dynamics 365

New API Limits for Dynamics 365 will be enforced soon. Below is a link to help you to understand these limits. But the key informatio is that "Yes, all existing customers will have a transition period until October 1, 2020 or the expiration of their current subscription term, whichever is longer.". So please make sure you dont miss this information.

https://docs.microsoft.com/en-gb/power-platform/admin/api-request-limits-allocations

Unified interface Transition Dynamics 365

Unified Interface Transition is coming soon!

The below playbook contains a lot of documentation to help you with the transition.

Highly recommended.

https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/unified-interface-playbook

CDS Data Integration with Azure Data Lake

Its still in preview but its a big deal. Very useful scenario for Power BI, Machine Learning techniques etc. Please see the link below for more details

https://powerapps.microsoft.com/en-us/blog/exporting-cds-data-to-azure-data-lake-preview/


Demo: https://powerusers.microsoft.com/t5/Microsoft-Business-Applications/Common-Data-Service-Seamlessly-enable-CDS-entities-for-analytics/m-p/299029

CSV File Reader / Write to a CSV File

Recently we came across a great csv helper Nuget package libararry from Josh Close. You could easily find it in the Nuget solution search. I would highly recommend it. Its an incredible option to read CSV and Write to a CSV file as well.I have used it for both of these scenarios and the reading / writing was very easy. Works very well with Azure Functions, Web jobs etc. Simple examples can be found on the below links.

https://joshclose.github.io/CsvHelper/getting-started#reading-a-csv-file

https://joshclose.github.io/CsvHelper/getting-started#writing-a-csv-file 

Comparing Values on Parent and Child entity Records in Dynamics 365

Scenario: Parent entity record and child entity record were maintaining a unique value. Due to some technial issues, some child records got generated with a different value other than parent entity record value. The challenge was to find out the records which had a mismatch and then fix them.

Solution:
Created a calculated boolean field on the child entity record.
Formula for calculated field- Set the boolean field if child entity field is not equal to parent entity field value.
Later using advanced find, found out all the records which had the boolean field set. Exported them and updated the right values by referring the parent field value and imported back.