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
Deployment pipeline: Deployment rules for Direct Lake on OneLake semantic models
Currently, it is not possible to use deployment rules with Direct Lake on OneLake semantic models. The option is greyed out. Please enable this, so we can automatically change the data so...frithjof_v42 minutes agoCommunity ChampionNew6KViews137likes17CommentsNative Master Data Management Solution
Microsoft Fabric currently lacks a native Master Data Management (MDM) capability, creating a gap for organizations that need to manage and govern business-critical reference data such as customers, ...bradcoles1 hour agoRegular VisitorNew212Views1like3CommentsCopy results as markdown from data grid
When copying results from a query on the SQL Endpoint or Data Warehouse I often have to convert from the tab delimited table to markdown for sharing the results via services like teams or github. It...Tom_Fosterbi1 hour agoRegular VisitorNew3Views0likes0CommentsDeployment Pipelines - Remember selected stage
Every time we go into a deployment pipeline, it defaults to selecting the Development stage. I believe that it would be very rare to have a user select the Development stage. It would be helpful if d...PeterDaniels9 hours agoAdvocate IINew2Views1like0Comments