Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
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, when enabling PDF generation, all active Word document templates are made available for the respective entity, however this option is displayed and can be activated at any time in the process, but according to the customer's scenario, the quote PDF is only it could be generated and / or forwarded according to the status of the Quotation entity record (Active, or a Custom status of Approved).
Given this need, what would be your recommendation for the solution of this need.
I would like to emphasize that we have already tried to customize this condition through the features of the Workbench 2016 solution, common practice in consultancies, but the same rule did not work for the Generate PDF button, but it works for other native buttons, Deactivate and Create or a customized button.
Supporting references used for solution testing:
Mastering Ribbon Workbench 2016 - Part 5 - Hiding buttons conditional to the form context
How to Hide Button in Ribbon Workbench with CRM Dynamics 365
Thank you for sharing your question on communities.
At the moment, the button Generate PDF is not customizable in the same way we customize other out of the box buttons, we do have a limitation there. The only way to hide the buttons that is provided on the documentation is to disable the functionality for the whole entity as described here:
I'm not aware of other workarounds to perform this, but I will keep checking and updating the thread as soon as I find any.
I suggest that you also would update the ideas website with your requirement:
Hope this helps
After opening a case with the Microsoft support team we found a solution.
When using the Workbench 2016 tool, some commands were not being displayed and therefore we had no vision of the true command to associate with the anable rule.
During the explanation for the solution the Microsoft engineer Samuel Cavichioli presented me with some tips and tools to solve this case and now I would like to share with you:
At the end of the URL we must include the command "&ribbondebug=true" as shown in the image below:
Note that the page will be updated and the Command Checker button will be displayed, so we can debug the commands associated with the buttons, solution layers and their respective rules:
Note that the actual command for the Create PDF button is Mscrm.Form.quote.CreatePDF, this command was not visible in the Workbech 2016 tool. To solve this reported problem and edit the button's enable rules, the Microsoft engineer Samuel Cavichioli presented me with another tip.
According to the link below, I downloaded the Export Ribbon Definitions sample and extracted the environment definitions using Visual Studio, located the ribbon quote xml file, copied the original Command Mscrm.Form.quote.CreatePDF definition and pasted it into the definitions structure in the customization.xml file of the unmanaged solution that I created and exported to edit the ribbon according to the link below.
I added the necessary rules according to my scenario and the links below, then I compressed (zipped) folder with the edited files and I imported the edited solution back into the source environment.
Then just test if the applied rules are working through Command Checker according to the image below:
Business Applications communities