D365 Learnings - My Scrapbook | Kranthi Gullapalli

The most awaited feature for Power Apps portal is now available in public preview... This will open up lot of unexplored space in Portals.. Much needed and will be most used going forward. Below are the functionalities available in public preview Create Update Delete Associate and disassociate  More details in below link: https://powerapps.microsoft.com/en-us/blog/power-apps-portals-web-api-support-public-preview/

To keep this post short and simple. Trial instance which I created has MFA has been enabled  and while we are using the old method of login into XRMToolbox via Connection wizard, we are getting below error, as there is no possibility of a second level of authentication via Mobile. Below is stack trace and error encountered: Error : An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. Stack Trace : Server stack trace: at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean onewa...

In one of my previous blog post , I've explained how to retrieve data from CRM to Portal using OData. OData is the simplest way to retrieve the list of CRM records to Portal, but if you are not aware of the do's and don'ts then you might need to face a tough consequence for that. If we read carefully the Microsoft documentation it says below: The OData feed that is published is anonymous and does not have any authorization checks; therefore, it is important not to enable oData feeds for data that is unsuitable for anonymous portal access. So there is no possibility of adding an additional mechanism of checking for the authenticated user or not from the portal end. To conclude: Do not expose any sensitive data via OData to the portal via Dynamics CRM with Entity List configuration. Where to use oData: In case if the data to be displayed on portal is not sensitive such as displaying list of products in an e-commerce website or having a blog feed etc. Alternate Solution for s...

Yes, you read it correctly, if you go with default CRM configuration for Email token you might land up in a big soup... and the more delay you do to fix the issue, it will cause you more pain to fix the issue thereafter. This article is having below sections: Understanding of Token structure Understanding of Issue Security breach scenario Possible solutions Section 1: Understanding of Token Structure: As per Microsoft documentation ( Link here ), below is the Token structure As can be seen above out of 7 digits, the first digit is a deployment tracking number, second is to identify the user, and third is the actual counter having the count related to the number of emails sent Below are definitions from Microsoft, referred from the same article above Deployment base tracking number Configurable from 0-2,147,483,647. Default value is 0. Can be used as an identifier for a specific instance, organization, or deployment of Microsoft Dynamics 365. User number digit rang...

This could be a question for most of the people working on Dynamics Portals, but after a few days, this post might be irrelevant as everyone will be aware of this. Where do we manage Portal related development? Before UCI Upgrade: After UCI Upgrade: As everything is an APP now after UCI upgrade, navigate to the Apps section of your dynamics instance. Example URL:  https:// <your crm instance> .crmxx.dynamics.com/ apps Search for: Portal Once you launch the 'Portal Management' UCI App, you can see all the portal entities in the main left navigation. Hope this helps someone :)

Problem Statement: HTML or JavaScript changes made on to the portal were not reflecting on the portal until we made force restart of portal every time. This was very annoying for myself and other team members. Resolution: During our analysis, we found the following ways, which all are probable solutions considering different scenarios. Clear cache from Client browser: For this, the user logged into portal should have a Web Role of 'Administrator' to clear the Portal Cache. Below are the steps to Clear Cache a. Go to your portal and append this to your portal URL '/_services/about' in browser URL. b. Click Clear Cache button and check Enable 'Change Tracking' on the related Entity in Dynamics CRM. a. For this Navigate to CRM > Settings > Solutions > Your Solution > CRM entity associated with the caching issue. b. Enable the 'Change Tracking' checkbox as can be seen below If the above two options did not work then try this: Resta...

This post explains how do we change/map existing portal instance with one instance to another CRM Instance. i.e. Once you portal instance is provisioned how to map it to another CRM Instance. When do we consider this scenario:  When you are under tight budget and couldn't purchase more portal instances then we can map the available Portal instance to the required CRM instance and validate the portal functionality on new instance. We do not have any Sandbox portal available, all Portal Add-On's are of same price and it depends on which CRM instance we map it. Thing to Note: To manage CRM Portal instance, you need to be a global admin/owner of the Portal in Azure settings. Scenario: I have one Portal instance "Portal Instance - 01" which i need to switch from 'My CRM Instance - 01' to 'My CRM Instance - 02' Process to switch portal instance: 1. Go to Dynamics 365 Administration Center 2. Select Application Tab 3. Select the name of your p...