I'm a web, database, and network architect based in NYC, with specializations in the financial services, publishing, and SaaS sectors.
I build complex Marketo integrations for companies large and small... and can make Marketo forms and emails do things you never thought possible!
Check out my blog at https://blog.teknkl.com, which has Marketo-specific technical insights you won't see anywhere else, along with wider topics from my programming and systems work.
customObjectName, filterType and we get an appropriate error if we enter invalid values against those fields.These are enumerations of property names, not data values in the databa...
It's neither a bug, nor is it "good to have" — because you're not understanding how the Marketo database works.It's a terrible to have feature that would break the system. It would...
in all other scenarios we have worked beforeReally? In all other databases with an email column, a query against that column is validated? Against what regex?Don't think so. Anyone...
"123" is a valid Email value. Nothing wrong there."abc" may not be a valid hyphen-grouped GUID format but I've never seen a single system that does format validation on this dataty...
From your DM it sounds like you solved this, but in case anyone is lurking data-wrapper-for="mktoCheckbox_19403_0 ourCheckboxFieldName" data-wrapper-for="mktoCheckbox_112345233_0 o...
I agree that this would be useful, but an easier workaround is to use the Push Lead endpoint, which specifically contains a Reason field as part of the call. I use this to contain ...