Skip to main content
Microsoft Idea
Liquid error: Exception has been thrown by the target of an invocation.

Vote (0) Share
's profile image

on

Comments (Liquid error: Exception has been thrown by the target of an invocation.)
's profile image Profile Picture

Olesia Lyfar on 23 May 2024 22:44:16

RE:

This would make the approach so much simpler and intuitive

's profile image Profile Picture

Olesia Lyfar on 23 May 2024 22:42:27

RE:

This is critical functionality for us

's profile image Profile Picture

Jonathan Boarman on 23 May 2024 22:16:29

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

's profile image Profile Picture

Tyler McClain on 23 May 2024 20:08:49

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.

's profile image Profile Picture

Tyler McClain on 23 May 2024 20:06:06

RE:

The ability to create unique experience would significantly increase if this was possible in the journey designer.

's profile image Profile Picture

Tyler McClain on 23 May 2024 19:51:37

RE:

Duplicate idea, please up vote this idea https://experience.dynamics.com/ideas/idea/?ideaid=a4a07397-a977-ee11-a81c-000d3ae53364

's profile image Profile Picture

FABIAN RAYGOSA on 23 May 2024 19:11:26

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.

's profile image Profile Picture

Tyler McClain on 23 May 2024 19:02:02

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

's profile image Profile Picture

Jonathan Boarman on 23 May 2024 18:44:07

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?!?!

's profile image Profile Picture

Jonathan Boarman on 23 May 2024 18:42:28

RE:

Is there a timeline for when this is expected to be placed on the roadmap?