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've noticed that the Advanced Find Command button has appeared on our Dynamics 365 instance. It was not there before and we've seen all our other environments and it is never displayed there.
Has anyone else come across this appearing randomly, and also not working?
Thanks in advance
Usually that button does not appear at the position displayed in your picture. Have you initially configured that with the Ribbon Editor solution/tool?
Thank you for your quick response on this.
That is what we are baffled about. We've not changed anything on the ribbon workbench. We recently did a solution drop, from a staging environment and since then its appeared. But in Staging it is not there...
Then it still looks like that it comes from the last solution you deployed on your other Dyn365 instance.
You could unzip the solution and check in the customizations.xml file if there is any RibbonDiff or RibbonDiffXml tags includes that point to the advanced find and refresh all button as these buttons should not appear at this spot on a vanilla system.
If so remove it, zip the files together again and try to import it on a test instance to see if that was the reason.
Thank you. I can do that, however why would it have come from the solution when the staging environment does not have the button? This is an unmanaged to managed solution.
Reasons could be human error, manual changes in the default solution or unmanged solution.
Thats why I would try to export the solutions and compare the contents of the RibbonDiff tags.
Business Applications communities