Form Events Not Firing: Browser Development Tools are your best friend
Read the latest from our developers as they share their real world experiences with Form Events.
I’m no stranger to a Solution having issues after importing and reimporting several times in CRM Online… this seems to me to be a bigger problem than older On-Premise installs. I’ve even seen several cases where an entire online Sandbox instance needed to be reset, through no user fault. So I started researching online and soon saw people saying that occasionally Microsoft reps will tell folks like us to comment out the “InternalHandler” nodes for issues like this in the customizations.xml file itself (inside the solution zip file). So, I went ahead and commented some of those out and tried to reimport… then tried again taking out other handlers… tried different combinations of changes, etc. No dice.
At this point I was starting to sweat, as we were on a tight timeline and starting a case with Microsoft would have been an unacceptable delay. I kept poking around the customizations.xml file in hopes I would spot something out of place.
So get this: I think CRM actually saved the metadata on the web resource with the wrong file name. I was at my wit’s end rooting around an exported test solution when I saw this:
Obviously this is useful only at the server side, so they’re adding on their own GUID to the file name. However, I noticed the last two letters of the word “Number” were missing. Probably just an intended cutoff to limit file name size, right? Well apparently no cigar! I corrected it by adding the “er”, reimported and it all started automagically working again. Note that this was a separate import attempt with no other changes, so I can’t see what else could have caused this improvement. If they did intend to limit filename length, they didn’t pen up all their pigs.
Now I have to give the caveat that I haven’t been able to prove this out full circle as it may be a while before we see this problem again; but, if I’m right about the file name being involved, that is definitely a bug, and if I’m wrong, the solution import process is definitely somewhat unreliable. So either way, something to keep in that back pocket where you keep the Typhoid Mary’s of the CRM troubleshooting world.