Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I create a workflow step that run every 11 hours after process-Execution Time ,
it's work nice but sometime i don't know why , i have error like this in below pic
could you please help me to resolve this problem or suggest me another way to do that (i want update some field in form when exchange rate had changed , and with the new value of exchange rate all of calculated field must be change )
this is detail of error
[Ayco.SetCurrencyForFI.Workflow: Ayco.SetCurrencyForFI.Workflow.SetCurrencyForFI][Ayco.SetCurrencyForFI.Workflow (18.104.22.168): Ayco.SetCurrencyForFI.Workflow.SetCurrencyForFI]
System.IO.IOException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #82FB193F
Unhandled Exception: Microsoft.Crm.CrmException: System.IO.IOException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #82FB193F at Microsoft.Crm.Sandbox.SandboxCodeUnit.Execute(IExecutionContext context) at Microsoft.Crm.Workflow.Services.ProxyCustomActivity.Execute(CodeActivityContext executionContext)
Looks like it is failing when trying to do an IO Operation. Can you check this method SetCurrencyForFI and see what it does? Since the issue is intermittent and failing with an IO Exception i'm not sure you will be able to catch it in a profiling session and debug it via Visual Studio. Maybe you could add some extra logging to the code to help you narrow down.
Business Applications communities