fbcideas_migusr
2 years agoNew Member
Status:
New
Notification or Alert when Direct Lake refresh failed
It seems that when Direct Lake encounters an issue (such as a table not being found as a result of a drop → Create operation), the "Keep your Direct Lake data up to date" option is automatically turned off.
This could lead to potential data loss or outdated data being used without the model administrator's knowledge.
Therefore, I propose a feature that notifies the model administrator when this option is turned off due to an update failure. This will ensure that administrators can promptly address the issue, preventing any unforeseen consequences or errors in the data.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v12 hours agoCommunity ChampionNew616Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v20 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019723 hours agoFrequent VisitorNew6Views0likes0Comments