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
I my recent practice, I've been used to customizing the OOB forms to best keep things out-of-the-box. One of the concerns I have is - Is there a significant issue if we don't use OOB "Project Information" forms provided by PSA?
Or is it recommended to continue to use our Unmanaged forms?
Kindly share your thoughts.
Thanks in advance.
Which forms do you specifically have in mind and why do you want to use new forms instead of what's provided OOTB?
Personally, you would have to have a very strong argument for me to even remotely consider dismissing the OOTB forms. But that's just me :)
Haha! So the scenario is we previously started using the custom form on top of PSA with the impression of "Let me take just what I need, we might not need every feature of PSA just yet". Although nothing looks suspicious so far.
I'm looking at Opportunity, Quotes and so on.
Quickest I can think of is having to set the Types to "Work Item" from behind the scenes. I'm doing an analysis of what else in the Sales Process of the same could I miss if I happen to miss the OOB forms and stick to custom forms.
Well with opportunity to quote to project contract it's mainly the flow of customer data. Then there is the price list logic and how that flows through the "PSA process".
With oppo you want to think of project based lines and naturally the PSA quote is converted to project contact. I want to say the PSA quote has a lot of functionality.
In my opinion you don't lose much on the opportunity. The question is how do you push data from oppo to quote?
The majority of cases I face have an oppo form based on the sales app. Usually this has been implemented a long time before PSA. In these cases customers usually just start the PSA process from the Project Contract. Based on my observations not a whole lot use Quote as quotes are usually made in a different system. But this can't be generalized as there seem to be business culture differences in the way quotes are made and structured.
I see. What you say is pretty insightful. Well, there are also a few customers who want to use Opp & Quote as traditional "data containers" than actually taming what they're meant for in PSA. And hence, 'keeping it simple' approach to not really explore capabilities provided by PSA.
I often see users not trying get the best out of the system and instead preferring to just hold data because they feel it is a great learning curve to get into the process. That's what I've observed.
But yes, what you say Antii, does make sense and can give great benefits if PSA is used smartly. Trying to adapt at least to some extent to the system too is as necessary as it is to make/configure/customize the system according to business needs.
Business Applications communities