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
Proactive Alert Notification Before Capacity Throttling in Power BI / Fabric
Currently, Microsoft Fabric / Power BI does not provide a built-in, native alerting mechanism to notify administrators before capacity throttling occurs. While the Capacity Metrics App helps moni...MSReshma5 hours agoMicrosoft EmployeeNew1.1KViews17likes2CommentsIn Fabric view, let us assign workspace colors based on stage (dev, test, prod)
Currently, colors are automatically assigned randomly. It would be nice if your dev workspace was always blue, and your prod was always pink for example. Then you'd have a good visual as t...jsatow7 hours agoAdvocate INeeds Votes1.3KViews99likes3Comments