Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
We are using Project Service Automation and we have gone through the process of Lead > Opportunity > Quote. In the quote line details, we can see all the details that we need for the project.
The quote is accepted by the client and we want to then generate a project and work breakdown structure from all the information already entered to this point. We can create a project contract... but no project.
Any help here would be great!
In PSA a Project Contract and a Project are their separate "containers". The default OOTB logic is that you create a Project by:
A) Creating it from a Quote Line on a Quote OR from an Order Line on an Order.
B) Separately and then associating it with a Quote or Order Line.
When a Project is being created you can choose to create it from an existing Project Template. This way your Project will follow a predefined WBS. You can import tasks from a Project's WBS on a Quote/Order Line but not the other way around (from Quote/Order to a Project's WBS). In PSA the idea is that you can either create a high level estimate manually or import from Project estimates.
Please see example photos from PSA V3 below. The logic is the same in V1 and V2.
Business Applications communities