Personalized Community is here!
Quickly customize your community to find the content you seek.
Automatic Update Policy for Project Service
The Project Service (PS) solution will enable system-driven, automatic updates, in alignment with other Microsoft announcements that have highlighted the improved update process for Dynamics 365.
Learn more about Automatic Update Policy
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 1 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
Today I'm trying to create a new project record using the create project activity when a field value on the create project entity is set to YES.
When I test it I get no errors and no new project record. Running it in the background doesn't work either. If I set the workflow to run on demand it works perfectly but this may not go over well with my click-averse crowd.
Is there a trick to using the create project with real-time workflows?
No, it's related to Project Service.
What I'd like to do is send a task to create a project to a project manager/team whenever an order is created. There is an activity called "create project" that I can use for this.
My plan was to add a yes/no field to it. If that field is marked "yes" then a workflow would run to create a new record in Project. Problem is the real-time workflow didn't work and also didn't throw an error telling me it didn't work. Is it possible it did fail and just didn't show a business process error dialog box?
I was able to set my workflow to run on demand and call it from within create project using the run workflow command. That takes about 4 clicks.
Thanks for your responses, Antti. My apologies for the delay getting back to you.
I think it had to do with what I chose to use for the project manager. I chose a team instead of an individual user. In System Jobs there are failure notices but no dialog box popped up so it wasn't immediately obvious the job failed.
I'm trying this again by calling an on-demand workflow from More Commands within the task and I get a new error: 'This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again. For information about workflow logic, see Help.'
This is what gets repeated:
Starting sync workflow 'Actual end date validation', Id: 58ca292f-5b42-e811-a956-000d3a14431b
Sync workflow 'Actual end date validation' completed successfully
Starting sync workflow 'Due date validation', Id: a52b2235-5b42-e811-a956-000d3a14431b
Sync workflow 'Due date validation' completed successfully
Entered Microsoft.Dynamics.ProjectService.Plugins.PreProjectCreate.Execute(), Correlation Id: 76469a4a-992e-49a1-b932-31561c29701e, Initiating User: 02b62fac-ee29-e711-8110-c4346bad9668
Exiting Microsoft.Dynamics.ProjectService.Plugins.PreProjectCreate.Execute(), Correlation Id: 76469a4a-992e-49a1-b932-31561c29701e, Initiating User: 02b62fac-ee29-e711-8110-c4346bad9668
Starting sync workflow 'Project: Create a Project On Demand', Id: 64998bec-46b1-e811-a967-000d3a1993e0
Sync workflow 'Project: Create a Project On Demand' terminated with error 'This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again. For information about workflow logic, see Help.'
I didn't create this activity "Create Project" I stumbled across it in the drop down list one day.
My workflow project form is below. I added variables that add on to the created date for the project to populate the Due Date and Actual End date. That's not helping.
Hello, let your workflow NOT put values into Estimated Finish Date and into Actual End. This should fix it. If not, also do NOT put values into Actual Start. It should be enough to put value into Estimated Start. Then the PM will create the WBS/Schedule and this will drive Estimated End. Actual Start and Actual End get updated automatically also as project progresses. I hope this helps.
Thanks for your help!
Business Applications communities