ncalinoi
9 years agoNew Member
Status:
Needs Votes
Use SOQL relationship syntax for Salesforce object queries
When loading data for a child object in a parent query (e.g.: loading opportunities with Account.Name child values), two separate SOQL queries are currently generated (with independent series of REST API calls), one for the parent and one for the child. Network traffic and overall payload size would both be considerably reduced if the relationship syntax described at https://developer.salesforce.com/docs/atlas.en-us.204.0.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_relationships_understanding.htm were supported.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara1 hour agoNew MemberNew16Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels8 hours agoAdvocate IIINew185Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen9 hours agoAdvocate INew299Views47likes2Comments