Marketo String field character limit | Community
Skip to main content
June 12, 2018
Question

Marketo String field character limit

  • June 12, 2018
  • 2 replies
  • 6568 views

Hi,

I have a question regarding the String field 255 character field limitation...

It seems that when a String field gets updated from a CRM synch (in this case Salesforce), Marketo ignores the 255 character limitation. I ran some tests with a Salseforce Multi-select field mapped to a Marketo String field, and the Marketo field captured the full 860 character value (example below).

If I write to the same String field from an integrated web form, the character limit applies, and the value gets truncated at 255 characters.

Does anyone know if this is a matter of data priority - so any updates from a CRM synch to Marketo field would override the character limitation rule?

Thanks

Timo

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Josh_Hill13
Level 10
June 12, 2018

Seems to be a special case for SFDC to override.

SanfordWhiteman
Level 10
June 13, 2018

If I write to the same String field from an integrated web form, the character limit applies, and the value gets truncated at 255 characters.

Mmm, not always, depends on how you add the field to the form. A hidden String field can store 2000 characters.

Actual length and precision of Marketo datatypes is almost never what's documented.   Needs a whole overhaul and some major fixes (like Floats are totes broken).

June 13, 2018

Thanks, this is interesting.

We are using the API to write data from an externally hosted form to MKTO, and one of the fields (a multi-select) can potentially exceed the 255 charcter limit (depending on how many preferences the user selects).

When you say a hidden String field can store 2000 characters, are you referring to the MKTO DB field? If yes, then how would a MKTO user be able to segment on that field (i.e. to build Smart List filters)? I was under the assumption that hidden fields in MKTO are not visibible for Smart List filters.

It would be great if we could write data from a hidden form field to the standard (non-hidden) MKTO String field without the 255 charcter truncation. Would a hidden form field override this 255 charater rule, the same way it does with the SFDC synch? I would assume no.

SanfordWhiteman
Level 10
June 13, 2018

A hidden field on the form. Not hidden in the db. Hidden on the form means it doesn't use a length-validated input box.