It would be good if the Fabric REST API supported odata filters when retrieving all items.
As an example if I want to get the ID of a workspace by name using the Fabric REST API I need to call
https://api.fabric.microsoft.com/v1/workspaces/
to retreive all workspaces that the caller has access to and then iterate over the list in the calling application to find the desired worksapce.
However in the Power BI REST API I can simply call
https://api.powerbi.com/v1.0/myorg/groups?$filter=name eq 'my-workspace-name'to retreive a result set with just the desired workspace (or an empy resultset if the workspace does not exist or the caller does not have access to it. This would avoid the need to handle paging in the caller and enable simpler logic.
Also I am aware that at the moment I can call the Power BI groups end point to retreive workspaces assigned to a Fabric capacity but having to swap between end points because the Fabric endpoint has less functionality feels less than great also for my specific use case that prompted this post I need to retreive notebook IDs by notebook name.
I am sure there are other folks out there who also need to get Fabric only items that would benefit from the Fabric REST API getting closer to feature parity to the Power BI REST API.
No CommentsBe the first to comment
Recent ideas
Enable OneLake to Read Snowflake-Managed Iceberg Tables via Horizon Catalog
1. Current Problem Snowflake lets customers create Iceberg tables where Snowflake manages both the catalog and the storage (CATALOG = 'SNOWFLAKE', EXTERNAL_VOLUME = 'SNOWFLAKE_MANAGED'). This is th...NareJoshi5 hours agoMicrosoft EmployeeNew3Views0likes0CommentsSet SQL analytics endpoint access mode (User's identity) via REST API and Terraform
The SQL analytics endpoint enforces OneLake security only in User's identity access mode. The only documented way to choose the mode is the Security tab in the portal (Data access mode settings). Not...smorimoto9 hours agoNew MemberNew2Views0likes0Comments