Archaeology – Finding CRM SDK History

The author of the article discusses the challenges of working with different versions of Dataverse (or XRM/CRM) and the lack of a comprehensive feature/version/metadata matrix. They explain that when creating new features, they often receive error reports from users with older versions of Dataverse. To address this, they share their approach of adding updates to their tools to fix problems and ensure compatibility with different versions. However, they express frustration at the lack of a centralized resource for finding the information they need. The author then describes their search for a solution, including reaching out to the community and Microsoft experts. Ultimately, they find a tool called PackageHistoryBuilder that allows them to decompile and analyze different versions of the SDK library to determine when specific features were introduced. They also provide an example of how they used the tool to analyze the history of the FetchXML Builder. The article concludes by emphasizing the importance of building tools that will work across different versions and expressing the need for an "archaeology" tool to understand the history of SDK development.

Article 37m Jonas Raap

---

Login now to access my digest by 365.Training

Login