Will a second form submission stop an email drip from the previous form submission?

[Anonymous]

In my current case I have 5 products.

But that could easily increase over time.

The client does not like the individual checkboxes, and prefers the dropdown.

But I might be able to persuade if there's a solid functional reason.

[SanfordWhiteman]

Even if you use a (single-select) dropdown, you can still use it to manage a single semi-colon delimited field. You would use the Forms JS API for this, and I definitely would prefer that to managing concatenated fields on the back end.

But more to the point, this is still overengineering even if you let the field have only one value at a time.  If a Data Value Changes trigger brings someone into a flow, they don't get booted from the flow if the value changes again later. They're already in the flow.  And you can (and probably should) be using list or program membership to permanently record their interest anyway.

[Anonymous]

Compiling lists based interest sounds good.

One question:

If I make a list for people who choose product A, all those people get put there.

If one of them then chooses product B, they get put in the list I make for product B.

Do they get removed from the list for Product A?

[SanfordWhiteman]

If I make a list for people who choose product A, all those people get put there.

If one of them then chooses product B, they get put in the list I make for product B.

Do they get removed from the list for Product A?

Of course not! I think you have a preconception that Marketo has these mutual exclusivity rules. While that's true in certain cases (like a single text field) Marketo is by and large a one-to-many system.

[Anonymous]

Yep.

[Anonymous]

Just to be clear, I would switch out the current Product Interest field for a Product Interest Temp field?

[Anonymous]

Yes, this way you'd be able to store multiple product interest values in "product interest" field, if that's what you want. If you have very few products then you should probably follow Sanford's advice and create several fields, but if you have dozens of product creating a distinct field for each one of them probably would be a management hell, so my proposal would work best.

[SanfordWhiteman]

but if you have dozens of product creating a distinct field for each one of them probably would be a management ****, so my proposal would work best.

But you still don't need a formal history field if nothing else is being historically recorded (i.e. you're not adding {{system.datetime}} or other metadata to history entries).

You can have a multi-valued Checkboxes set in that case, which Marketo will automatically manage as a semicolon-delimited field. 

[Anonymous]

I'm a bit lost in writing this rule.

Am I on the right track here:

[SanfordWhiteman]

This step (the way you've started to build it out) won't do what you expect.

If you must maintain a history field, your Smart List triggers on ​Data Value Changes - Last Product Choice (see no reason to call it "temporary," it's simply the last submission).

Then your Flow sets Product Choice History to {{lead.Product Choice History}};{{lead.Last Product Choice}};, simple as that (the surrounding semicolons are purposeful).

But I still feel you're overengineering this.  Remember how many other fields you'd have to manage this way as your instance matures, if this becomes the standard method. Simplicity should be your guide and I don't see the upside here.