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?
fbcideas_migusr
6 years agoNew Member
I agree, not least because this would let us run FetchXml aggregate queries on the CRM-side
Recent ideas
Pipeline: Activity-level Run Conditions (No IF Container Required)
We need the ability to add a "Run if" condition directly to every pipeline activity. Like, in each acticity's settings. One of the biggest readability issues in Fabric Pipelines is that conditional ...frithjof_v1 day agoCommunity ChampionNew25Views3likes1CommentPipeline: New Routing activity as an improvement to IF and Switch
The current If Condition and Switch activities create large nested containers that own all activities inside their branches. These containers make the canvas much harder to read. Instead, add a lig...frithjof_v1 day agoCommunity ChampionNew14Views1like1CommentEnhance Workspace Throttling to Allow Targeted Limits on Individual Workspaces
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } The current workspace throttling design should be enhanced to allow Fabr...kyleleonard1 day agoNew MemberNew29Views5likes0Comments