Controlling fields & restricted picklists in SFDC

[Anonymous]

I feel like i should specify, the \n is not actually appending to the data in the field (in marketo or sfdc) but rather, appearing appended to the selected value in the error message (as listed above.) After some list loads, we changed the value directly on the record in marketo - so selecting a different value from the picklist, this also generated the error message. my hypothesis is that the changes in SFDC somehow affected the available field data values in Marketo, causing it to throw this error...

[SanfordWhiteman]

OK, so the "\n" is just an artifact of log output and doesn't actually have anything to do with the issue. (It thus results from double-encoding at some point.)

So with that gone, what is unexpected now?  I'm confused. Either the record matches the picklist exactly and still throws an error (which is weird) or your picklist values are out of whack (which might have a unknown origin, but right now the system is working correctly).

[Aaron_Dear]

Are you still getting this error? We are too!

The Salesforce record doesn't have the "\n". The Marketo record doesn't have the "\n". But the error message notes that the field's value has an "\n". So odd.

I'm about to delve into a related Salesforce flow that might be culprit. This link talking about the uses of "\n" can help explain why this appears technologically.

[SanfordWhiteman]

But the error message notes that the field's value has an "\n". So odd.

Are you sure that's what it's noting? The posts earlier indicate that's just literal text in the log line for the error. Doesn't mean it's ever been in the field.  For example, if I clip out a line from a text file, I may or may not include the \n that's always at the end (except for the very last line). If you print that line and unescape the \n that doesn't mean it has any relevance to the content.

I feel like \n (whether a literal newline or a quoted "\\n") isn't the problem here.

[Aaron_Dear]

True - perhaps the log line for the error is all that it's displaying. That said, it's still blocking the sync to Salesforce.

I looked in a bit more, and only got more questions. For others who run into this issue and are frantically Googling to get through it:

We currently update this custom lead source field (an SFDC picklist) via the UI, through a Change Data Value flowstep. The field itself in Marketo shows the correct value. But we get this restricted picklist error (and a subsequent inability to sync back) regardless. The Salesforce lead record does not have the added field values, so we've confirmed that it has not been syncing.

No clue what the solution is. C'est la vie!

[Incynthia_Truon]

bumping this back up. 

has anyone found a solution for this? we are bumping into the same issue and noticed that on occasion the /n does not get appended but still fails.

[John_M]

Did you ever crack this one? I'm seeing something similar and I'm stumped.

[annaks]

I came across pretty much the same issue; noticed that when directly picking a value from the picklist (populated via SFDC) I get no error, but when importing the value or typing it in I get an error.

I used the DevTools to inspect the SFDC picklist values - open a person record, "open" the picklist of the affected field, righ-click on the picklist and inspect. We are getting our values with a ​ appended, this is causing the issue. While the value looks idential on the UI, SFDC does only recognize the value like that. We are currently checking on SFDC side to fix this, so the values are plain text. 

Maybe that helps?