Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We are on CRM 2015 On Premesis, and our MS SQL Server is setup with two replicas in an Always On Availability Group. I've enabled Read Only Routing so Intent Read Only connections will go to the Passive Replica, and I'd like to setup the CRM SQL Reports to use the Passive Replica. Problem is when I go into the CustomReport folder and edit MSCRM_DataSource the Data Source Type is 'Microsoft Dynamics CRM SQL' and Connection String is 'MSCRM Data Connector Connection String'. I did update MSCRM_DataSource in the Organization folder (same folder as the CustomReport folder), but apparently this isn't used by Custom Reports.
How can I update the connection string for Custom Reports to add ApplicationIntent=ReadOnly ? Or is the only option to create a new data source in the CustomReport folder with a direct connection to the AG? Also note this is only for SQL Reports using Filtered Views, not FetchXML Reports.
I am also having the same issue. Did you ever find a fix for this or does anyone else have any ideas?
Did you ever find an answer for this? I'll be doing the same for our 365 On-Prem deployment. Any response is appreciated. Thanks.
I guess it's my turn this year - Any one have an answer to this? Hoping to implement a solution while upgrading to On-Prem version 9. Thanks,
Business Applications communities