Grégoire_Miche2

Hi DanI have never seen "munchtions" in action -Greg

Hi Dan,Isn't it in MSD the equivalent of salesforce formula fields ?It will probably not solve your problem, but just in case: in SFDC, the way we solve this is we create a formula field that just copy the name of the lookup record. For instance, let's say we have a lookup field called "product" tha...

And also, it will not fire on lead creation, only on updates.-Greg

Hi Andy,One of the main limitations of the "data value changes" constraint is that it does not give the form ID nor the form name, just the URL. But it's better than nothing Just added this idea: -Greg

Hi Andy,It does not solve all the cases, but on the "data value changes" trigger and "data value changed" filter, you can use "Reason" and "Source" constraints.Source will need to be "Web form fillout" to filter the changes that are due to form fillouts.Reasons includes the URL of the LP.E.g.:Reason...

Voted and added there: Just do it! Marketo so-called minor missing features -Greg

Hi Robb,Thx a lot. I think I got it. Cast 4 will be: in you were sent Email 2b, send email 3. If you were sent email 3 and didn't open it, send 3b. If you opened email 3, send email 4. In fact, you do not need to test email 1, because it's "embedded" in email 2b and 3. Meaning that on cast 5, you wi...

Adding the possibility to set tokens values from within a flow step.-Greg

Hi Robb,You method works, but I still see 1 major problem: at each cast, you always add 1 more "if". After 10 or 11 casts, this becomes a pure nightmare.The method I propose makes it much simpler. You get the email or you are moved to next content.-Greg