And that’s until I ran into this article just a few days ago:Īs it turned out, it’s not just supported. Even if I felt somewhat guilty every time I’d be doing that). That’s what I used to be thinking (but that’s not to say that I would never update customizations.xml manually, though. So, manually updating that file must be unsupported, right? After all, we are supposed to configure Dynamics using the “customizations” interface. For example, there are over 11000 lines in the customizations.xml for the TCS Tools solution: That’s quite a few steps not to mention that the file itself looks rather complex if you’ve never seen it before. Then package everything into a new zip file.Find “customizations.xml” file in the folder.Add all the necessary components to that solution.That was sort of my gut feeling since, after all, that file is rather complex, and it’s not something you can edit easily – you have to go over a few steps to even get that file, and, then, you have to go over a few more steps to put it back to Dynamics:

I’ve been always wondering if editing a customizations file should be considered an “unsupported” customizations.

Best xml editor for word ribbon