Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
before i ask for help about specific problem i'll write short review of what happened.
We had CRM 2013 on-premise and i was able to debug workflows with Plugin Registration Tool 2013 (ver. 18.104.22.1683) after upgrade to CRM 365 (Version 1612 (22.214.171.124) (DB 126.96.36.199) on-premises) PRT from SDK 2013 was not able to connect to new version of CRM. So now i can connect to CRM only with PRT from SDK 2015 or newer but then i'm not able to debug workflow anymore.
Problem on PRT 2015 or newer is that steps are not visible when i try to profile workflow.
What are the options?
When you're on-prem you have possibility of direct troubleshooting - attach your VS to AsyncService. I'm afraid that this is the only way for you.
Pls try with CRM 365 PRT and connect using deployment administrator access account and check it.
Does attaching to AsyncService interupt CRM in any way?
You can either install or attach remotely - docs.microsoft.com/.../attach-to-running-processes-with-the-visual-studio-debugger
Attaching to AsyncService will block execution of async jobs for the time of troubleshooting.
Who is Deployment manager? Where can i see that?
This option works well.
Business Applications communities