Hi, Currently if we hit the refresh button then it goes to all the sources and update all the tables, eventually taking time if we have a big data source. So i was wondering, if it can be customized per source or per table basis. That is user should be able to choose whether they wants to update all the tables or a particular tables, It will save a lot of time during developing phase since a lot of trial and error goes at that phase. Best Wishes, Sami
2 Comments
- mdmoo1978Regular VisitorIt would also be nice if Data Gateway refresh frequencies could table based. Our data is big and some pieces need to be updated multiple times per day, others once a day and some once per week or month would be fine.
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Add support for identity columns in Fabric warehouses.
Identity columns are a common method for generating surrogate keys in data warehousing scenarios implemented on SQL Server. By adding support for identity columns in Fabric, users could migrate the...dpurdy6 hours agoRegular VisitorCompleted4.4KViews131likes11CommentsFabric UX Idea: Clearly Identify the Source Workspace for Opened Fabric Artifacts
In many Fabric implementations, organizations have multiple projects and environments, for example: Sales Analytics – Development Sales Analytics – UAT Sales Analytics – Production Similarl...Murtaza_Ghafoor12 hours agoSuper UserNew8Views0likes0CommentsCopilot in Power BI should be canvas-aware and support screenshots / direct visual debugging.
Currently, Copilot in Power BI cannot: See the actual canvas / selected visual Accept screenshots or images to aid in troubleshooting Both of these make debugging visual-level issues painful and...dcohare12 hours agoHelper INew12Views1like0Comments