RE:
-- select all referencable columns from all tables except t2.c4SELECT * EXCEPT(t2.c4) -- sometimes called "EXCLUDE", like in Snowflake and DuckDBFROMVALUES(1, 2) AS t1(c1, c2),VALUES(3, 4) AS t2(c3, c4);OUTPUT: 1 2 3
RE:
The feedback from MSFT administrator is frustrating. While this is already accomplishable through an exit segment.The customer problem is the following:You have to have identified a need for an exit segment before the journey is published. That is not isn't realistic for all journeys . Many times it's realized after the fact of people that should be excluded.You have to identify a dynamic way to bring customers into that segment since you can't manually edit or add someone to a segment once the segment is used in a live journey. This be complicated because additional configuration may be needed to accomplish this.It's also not realistic to be adding configuration to dynamically identify customers to exclude for every journey.
RE:
The ability to create unique experience would significantly increase if this was possible in the journey designer.
RE:
Duplicate idea, please up vote this idea https://experience.dynamics.com/ideas/idea/?ideaid=a4a07397-a977-ee11-a81c-000d3ae53364
RE:
this is a major customer facing problem.If someone comments about an issue and its fixed, admins should not ask original poster to delete. that's terrible business practice.The comment is then stuck there eve though its fixed.We should not be asking managers to delete their comments.Please allow admins to delete. This comment feature is extremely powerful but useless if anyone can comment and it stays there.
RE:
Please vote for this duplicate idea that has a larger number of votes at the time of this commenthttps://experience.dynamics.com/ideas/idea/?ideaid=830432f0-e9fd-ed11-913a-0003ff45ce96
RE:
I really hope this one gets more attention. This is crazy simple to do in Databricks and yet somehow not even feasible in Fabric?!?!
RE:
Is there a timeline for when this is expected to be placed on the roadmap?
RE:
This is on the public roadmap, with an estimated release timeline: Q3 2024.https://learn.microsoft.com/en-us/fabric/release-plan/shared-experiences#github-github-enterprise-support
RE:
If we think of gold and silver as "table qualities", then maybe folder is not an adequate structure in all cases. Sometimes, we could pull out the metadata on a table, e.g., TBLPROPERTIES("quality" = "silver"), then leveraging that convention to add a color or gold/silver/bronze badge to the object would be a better way to express table qualities.