I’m a big fan of Fetch XML. Unfortunately, to many, it can be frustrating. Anytime I’m at a conference and I talk about fetch being my preferred way to pull data, I unintentionally create an argument. I get that fetch is complicated. I agree that fetch barely has any of the features of SQL. However, fetch is still the fastest way to pull data from CRM and offers the most flexibility in retrieving complex information.
Note: As a reference for performance, if you ever used my CRM Data Detecitve tool, you’d know that aggregate calls are quite fast.
Why create a Fetch XML Editor?
Simple. To make writing fetch easier than ever. But if we’re making a fetch tool, we have to include some extra features:
- Editor with an intelligent auto-complete
- Fetch XML Schema validation to provide better error messages
- Tabular output with export to excel functionality
These are only a few of the features we’re actively addressing and here is a sneak peek…