D365 Learnings - My Scrapbook | Kranthi Gullapalli

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

I had a fresh installation of Windows 10 OS on my machine and downloaded the latest version of XRM Toolbox. I had got the below error when I tried to connect to the CRM Organization. Error : Metadata contains a reference that cannot be resolved: 'https://disco.crm11.dynamics.com/XRMServices/2011/Discovery.svc?wsdl&sdkversion=9'. Stack Trace : at System.ServiceModel.Description.MetadataExchangeClient.MetadataRetriever.Retrieve(TimeoutHelper timeoutHelper)    at System.ServiceModel.Description.MetadataExchangeClient.ResolveNext(ResolveCallState resolveCallState)    at System.ServiceModel.Description.MetadataExchangeClient.GetMetadata(MetadataRetriever retriever)    at Microsoft.Xrm.Sdk.Client.ServiceMetadataUtility.RetrieveServiceEndpointMetadata(Type contractType, Uri serviceUri, Boolean checkForSecondary)    at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1..ctor(Uri serviceUri, Boolean checkForSecondary) Solution: It turned out to be a network proxy issue. Follwed be