on
RE:
This is critical functionality. It will enable marketing to work more effectively by reducing duplication and create the opportunity to create targeted and scalable campaigns.
RE:
This would make the approach so much simpler and intuitive
RE:
This is critical functionality for us
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.