Xrm Setdisable() Does Not Work On Browsers Other Than Ie
Solution 1:
Try using XrmServiceToolKit new version which should support cross browser compatibility:
Solution 2:
If you are not currently on Rollup 12 then Chrome is not supported officially.
If you can, then I would try and upgrade to get the new cross browser support offered via Rollup 12. Make sure you check out the code validation tool to make sure your code and customizations don't have any issues.
If this isn't an option then you can try the xrmservicetoolkit which is a CRM JavaScript library.
Solution 3:
You need to update the roll-up of your organization to at least 12 (the latest at the moment). I'm surprised, though, that you got as far as to actually getting the error. You shouldn't be able to log in and display the "main" forms when using unsupported browser.
EDIT:
It's definitely not an issue with RU12 and browser brand. I just created a new organization and added the following functionality via a web resource.
functiondisableFullNameOnLoad(){
Xrm.Page.getControl("fullname").setDisabled(true);
alert("Full name disabled on load.");
}
functionenableFullNameOnSave(){
Xrm.Page.getControl("fullname").setDisabled(false);
alert("Full name enabled on save.");
}
As the nomenclature implies, the disabling is performed in the form's onload and enabling in its onsave. I entered the CRM (RU12, OP) using FF, IE and Cr. The behavior was consistent - greyed-out fullname as I open the form and editable when I save it.
So whatever issue there's on your platform, it's not directly related to cross browser incompatibility. Can you check again that you get the discrepancy in behavior between IE and FF when you add the exact code from my examples, connected to the events exactly the way I described, please.
Post a Comment for "Xrm Setdisable() Does Not Work On Browsers Other Than Ie"