Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
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
Just completed 8.2 to 9.0 upgrade for On Premise system. we had an HTML webresource in the page header (its a custom progress bar). When viewing the form it works fine and can be interacted with no problem as it was in 8.2, But when I go to the form editor and go to modify the web-resource, there is a place holder for it, but no ability to edit it, yet its there. (very strange) I have tried to re-insert the web-resource and that works fine, except now its duplicated and I cant delete the original one. Anyone seen this issue? any thoughts?
in the image below you can see the top web-resoruce has the resource name and is editable, below that is a box with no name and no editable properties . when form is published shows 2 copies of web resoruce.
I believe your last resort is editing of xml - create a solution that contains only the form you want to modify, export it, unpack, open customizations.xml and delete mentioned webresource, put to archive back and import to CRM, publish changes. If you've done everything in the right way unneeded webresource should go away. Don't forget that this approach is unsupported so store backups of your solution before you started changes. Good luck.
Andrew - perfect! - worked like a charm, thanks for the quick and detailed response -much apprecaited!
Business Applications communities