Allowing DataFlow objects with same name but in different folder (Purely from SDLC)
Allowing DataFlow objects with same name but in different folder. This is purely from SDLC life cycle perspective
e.g., in Fabric server DataFlow , we can have same object but in different folders with different parameters to enable smoother development and QA process. Limiting data for development and retaining more data to cover test scenarios are different SDLC situation that occurs in every single development irrespective of technology.
Dev Folder - Table_1
SIT Folder - Table_1
So that when we build versions of power bi dashboard, we point one with table_1 and publish inder DEV folder and vice versa against SIT folder.
This will enable avoiding creating multiple workspaces just for SDLC phases (like dev/qa/regression/uat/performance)
Recent ideas
Option to set custom width for gridlines OR fixed outer padding
When designing reports, using the align and distribute evenly options in the format pane are useful, however when designing report pages with fixed bleeds between visuals I have to follow these steps...IolaWhiteley8 hours agoAdvocate IINew2Views0likes0CommentsDefault Scrollable Time-Series Charts to Most Recent Data
Currently, Power BI time-series charts always open scrolled to the earliest (leftmost) date by default, which is inconvenient for reports where users are interested in the most recent (rightmost) dat...CStillwell9 hours agoNew MemberNew21Views2likes1CommentOption to Stop Fabric Planning Billing Session After Plan Item Deletion
Currently, a Fabric Planning session remains active for 30 days once triggered. If a user creates a Plan item only for testing and deletes it the next day, the billing session still continues and c...v-dugumarrir111 hours agoMicrosoft EmployeeNew47Views11likes1Comment