Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We recently upgraded to CRM 2016 On-Premise (with latest update) from CRM 2013 On-Premise. An odd form behavior I'm seeing is when creating new related record for custom entities in IE 11 at 150% zoom. The custom entity does not have a quick create form associated with it. So when a new related custom record is created it opens up the main form. After the main form loads two odd things happen: scrolling on the form can't be done either with the scroll wheel as well as clicking and dragging on the scroll bar on the left of the window, and the other thing is that clicking out of the field onto the form does something odd so that subsequent clicks on the form fields do not interact with the field like they should. Both of these things stop being a thing as soon as the record is saved.
I mentioned custom entity because I tested it on a vanilla Org and it would happen only for custom entities.
A couple of our users prefer things zoomed in for viewing purposes. And coming from 2013 On-Premise this wasn't a thing. I believe the supported zoom % is a 100 for IE and CRM so the workarounds I'm considering are:
Has anyone else seen this behavior and if so what solution have you come up with?
Have you tried toggle of the legacy form rendering to see result? You can read about here. Good luck. Tom.
This helped resolve the scroll lock challenge and the odd clicking on fields after initial focus, but then other challenges arose. The other challenge that pops up is that the field focus works differently. Where on form load it doesn't put any focus on any field initially so users have to click on the initial field to begin data entry and then tabbing between fields doesn't bring focus to the field properly (for at least lookup fields) so the user has to click on the next field or press enter.
So your suggestion seems to resolve the posted challenge, but provides a different resulting challenge that based on initial feedback end users enjoy even less. But this does help me understand what is going on and provide me with avenues to pursue.
Business Applications communities