Our lead assignment rules in SFDC are powered by specific values in a picklist field. We are also running alerts on contacts with the same data. Our SFDC Admin team has just has enabled restriction to the picklist values in those fields, so that we are notified in Marketo when the data isn't correct, and can fix it before it passes for assignment / alert. We are running into an issue where we cannot pass the values to the contact record, as somehow "\n" is appended to the value when we update them in Marketo, and then rejected by SFDC due to a mismatch with the restricted values. The lead data updates are working fine. Has anyone ever seen a similar issue?
For reference, the restricted picklist field on the contact record has a controlling field, whereas the lead does not.
Any insights would be helpful!
Are these textarea fields on the Marketo side?
Ah should have specified; the marketo data type is string.
And you're updating these using the UI, or an API?
we are updating them with the API
Then it stands to reason that your code is pushing a trailing \n.
The only way you can get a \n via the UI is if it's a textarea (which must support line breaks, by definition).
But \n is a perfectly valid character within a string, so if that's what comes in, that's what you get.
the typical way this data gets into Marketo is via a list upload or a form submit (form has picklist values.)
Where would the code that is pushing the \n be originating? Looking to understand if this is something we can fix via process enhancement or if it is a bug?
Also want to note - we are specifically loading values that we know to be correct into Marketo to test this.. that is the confusing part, somehow the \n is what is listed in the error message. For example, we loaded the correct value "GRC" but the error message shows the \n....
Please attach a spreadsheet, in your typical format, with some rows that are proven to throw this error.
Form post data from a select won't contain the \n.
List upload and form fillout (assuming Marketo form) are specially *not* API-driven methods. So you are not using the API to update Marketo, in fact.