While oData is a good start, it's both very limited and has a performance impact compared to the native FetchXML provided by MS CRM. Could we enhance the current connector to support Fetch?
6 Comments
- I agree, not least because this would let us run FetchXml aggregate queries on the CRM-side
- I agree
- I agree as well. Been trying to filter the amount of data that PowerBI Desktop grabs from CRM to just be the Trailing 30 days (I know there are filters that I can use after I get all the data, just want to make it so that I don't HAVE to grab everything), and apart from the Unsupported Refresh of Programmatically created OData calls There really isn't much to do.
- I agree as it will make CRM report developers life really easy. Using Odata functionality is taking much time to load tables and its tedious to modal your data where we have used option fields. Adding FetchXML features will definitely enhance PowerBI capabilities and speed up the process of creating dashboards and reports from CRM online.
- Agreed. FetchXML features would enhance PowerBI capabilities and steam up the evolution of constructing dashboards and reports from CRM online.
- Status added:Needs Votes
Recent ideas
executeDaxQueries-like API call with effectiveUserName on SSO-enabled model with Service Principal
Please provide a way for a service principal to execute DAX - with an effective user name - against an SSO-enabled directlake semantic model and get per-user results that respect lakehouse OneLake Se...
