RE:
Looks like MS shipped something similar, but not fulfilling core business needs. Here's the another improvement idea, that is (I hope) more specific towards custom pop-up for viewer access:https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=da99d80c-843f-ef11-b4ac-00224851bf7d
RE:
This is a requirement on a current project, are there any updates on this functionality being added to the roadmap?
RE:
Agreed, the way it is now makes absolutely no sense.I created an Idea a while ago which is sort of related:https://experience.dynamics.com/ideas/idea/?ideaid=b97ec32d-824a-eb11-8fed-0003ff689cf3
RE:
That would make our work way more efficient
RE:
Any update on this? It's now after Q2 2024
RE:
See this comment.It has some new lines and some code that looks nice in the editor:print("Hello Fabric")and a nice link: aka.ms/FabricRoadmapAll of it good removed :-(
RE:
Why would you need to load the data into the Warehouse via Notebook? You can write the data to the Lakehouse and directly query it from the WarehouseCREATE TABLE [research_warehouse].[dbo].[cases_by_continent]ASSELECT FROM [cases_lakehouse].[dbo].[bing_covid-19_data] caseshttps://learn.microsoft.com/en-us/fabric/data-warehouse/ingest-data-tsql#ingesting-data-from-tables-on-different-warehouses-and-lakehouses
RE:
Quick heads up
It's been a while since our last conversation, but I recently stumbled upon something online about microsoft.com and immediately needed to reach out to disprove this review.
It looks like there's some negative press that could be detrimental.
Knowing how fast misinformation can spread and hoping not you to be unprepared, I felt the need to warn you.
Here's where I found the info:
https://ibit.ly/RASFz
My hope is it's all a misunderstanding, but it seemed prudent you should know!
Wishing you all the best,
Blaine
RE:
Add my voice to the chorus of those who currently have a customer who intuitively expects this functionality to work.I'm curious what the purpose of the field on the Customer record is, if not to populate the field on the SO.Karla's comment is comprehensive and insightful, I can't say more or better than that.
RE:
I could see this is from 2019 already but now in 2024 it is still needed especially if we want to allow report creators to have rather more flexibility as sometimes the column can be relevant to a certain report but not to the other one connected to the same semantic model. It makes more sense to add it locally.