Well haven’t heard back from Salesforce yet on this one, but I did just see that this Critical Update has been delayed until the Summer 16 release.
https://resources.docs.salesforce.com/200/latest/en-us/sfdc/pdf/salesforce_spring16_release_notes.pd…
Check out Page 301
Not that I didn’t expect this or anything…
Thanks Ben. I find that, in new orgs, this update is activated automatically and it’s not available in the list of critical updates to then deactivate. Do you get the same?
Glenn, I feel like I’ve seen it both ways. But I think you’re right in most cases new orgs will have the Critical Updates turned on with no way to turn them off. I have access to a Spring 16 org right now. I’ll see if I can make this bug happen there when I get a chance.
I second what Glenn said. All of our new TrialForce customer orgs have this enabled by default and no way to turn it off, even though the TF Source org has it turned off. Salesforce essentially told me “too bad” when I logged a case about this.
It’s particularly frustrating that new user’s first exposure to our app is a blank screen and we have to tell them “just refresh”. I wish Salesforce would provide assistance with it.
Hey Everyone, another update on this. It looks like this is still not fixed in Spring 16. We decided to put some code into our Banzai Update 7 that will automatically refresh the page if the resources have not been loaded properly. Let us know if you still get this issue after installing Banzai Update 7.
Thanks for the update. It seems to be working much better so far.
I got notified by Salesforce that they fixed the underlying problem: https://success.salesforce.com/issues_view?id=a1p300000001ACTAA2
I haven’t tested yet, although the Skuid solution of auto refresh has been working for us.
1 Like
