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
Has anyone found a resolution for this error: The product cannot be saved because the parent cannot be edited?
In an opportunity with a product line creating a new quote results in this error. None of the products in our product lists have parents.
What do I need to modify to fix this?
Which version do you have? Have you installed any updates?
The parent in this case is the parent record where you are adding/ editing the product line example, if you are adding opportunity line then the related opportunity is closed which is why you are getting this message. Similarly if you are adding/ editing on quote the parent here is the associated quote which is closed.
Hope this helps.
Looks like you have custom code either plugins or workflow that appears to mark the quote as closed when it is created. When you create quote from opportunity, platform auto create the quote for you and then copies the line items from opp to quote, looks like before the lines are copied over the quote has already been marked as closed.
Could you verify the status of the quote that is generated?
This is exactly what it was, Sam!
(Can you tell me what shows that's the problem in the error message?)
There was an old on demand workflow that for some reason decided to run on its own. The MS tech I talked to thought it might have to do with recent updates.
Once that was deactivated everything worked fine.
Thanks for responding!
Thanks for responding, Ravi.
The quote was indeed closed.
Thanks for responding, Andrey.
We're running version 1710 (22.214.171.12425) online with the April 2019 updates enabled. Something in those updates seems to have triggered an old on demand workflow to start running on its own.
Business Applications communities