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 2 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
I'm looking to update some legacy code that utilises window.showModalDialog which is no longer supported by Chrome. The obvious solution was to replace this with Xrm.Utility.openWebResource as detailed here:
As per the documentation I have specified the width and the height of the resource and in Chrome this works perfectly. However in IE11 it ignores the parameters and instead always opens the web resource in a new tab. showModalDialog will open in a new window, which is what we want.
Here are my current tabbed browsing settings:
My thanks in advance for any assistance anybody is able to provide.
Forgot to add...
Selecting "Always open pop-ups in a new window" will open it in a new window but this may affect the user's preferences on other sites. As it stands, it's the only way I can see to overcome this issue.
I have not found any way around this limitation other than:
1. Refactoring the user experience to use a single page approach where it doesnt' matter that the webresource is in a new tab or replaces the current page.
2. Use an unsupported approach described by Andrii here - a33ik.blogspot.co.uk/.../step-by-step-creating-dialog-windows.html
Hope this answers your question
Thanks for the clarification, Scott - much appreciated. Due to the quantity of web resources in the system and the fact it's an online CRM instance, I'm loathe to use any unsupported approaches so will most certainly look at the former.
Thanks once again!
Is there any solution for this problem with CRM 2016? I have the same issue, opening a new window in Chrome works completely fine and honors the sizes sent using openWebResource
// Open web resource
window.parent.Xrm.Utility.openWebResource("sp_casetimer", customParameters, 500, 146);
In IE 11 it opens a new tab which is not desired.
It seems window.open works to get around this issue with IE. Kind of interesting the fix to make Microsoft IE work is to not use the Microsoft library. :)
Business Applications communities