Justin_Norris1

In addition to Greg's points, I would add a note of caution when considering using a separate product table and a junction object (i.e., many-to-many structure). Velocity cannot access the data on the custom object that is not directly connected to the person, and so you won't be able to pull from t...

Updated the post to include AI Lists, a feature I had missed. Thanks David Myers​

Brian Law​Regarding this point: When you import records into a static list that's a child asset of a program, records will automatically be moved to the first status in a programI just tested this to verify, and records do not get added to a program automatically when imported to a local list. Just ...

Grégoire Michel​Just to confirm, it appears you were right Greg - there were some unusual sharing rules in place that granted the sync user view access on the record (which allowed it to sync) but blocked the ability to edit the record despite having permissions on the field itself.

Sean Kennedy​It's an interesting question. There are five main approaches here that I am aware of. I've worked with them all with various clients, and they each have their pros and cons.1) Separate Programs for Offers and Channels In this case you create a distinct program for every marketing initia...

Thanks Greg.

Grégoire Michel​Thanks for confirming. Here's a sample of the activity detail: The message is especially weird as the sync user has access on the object and read/write permissions on the field. Waiting on support feedback...

Hi Grégoire Michel​, Regarding this: stop the sync FROM Marketo. Unchecking the "sync with Marketo" will propagate to SFDC at next sync, and from there, the sync will stop. The method you describe is our normal practice (to which I owe much to your posts here) and as I recall has worked correctly in...