Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
I have filed a bug for this issue, and the response from Marketo Support was to post this as an issue here. Background: Both Salesforce and Marketo allow carriage return/line feed (CRLF characters) in text fields. In SFDC, for example, users can type sentences, hit the Return key, and thus format en...
Of course! A rather embarrassing gap ....
Yup ... an Interesting Moment gets exposed to Sales via MSI. This is purely for administrator troubleshooting. Don't need Sales to see how the sausage is made.
Working with Marketo support, we came up with this workaround: We added a custom field to our SFDC user accounts: Sync to Marketo? Which does what it implies: in our instance, they introduced a rule to sync only user account records that were flagged this way. We then deleted (thousands) of records ...
Absolutely. It's just very disappointing that we can't build a smartlist that pulls in members of an SFDC campaign based on standard field values (such as "active"!) or custom fields. Of course, we also need them available as triggers too. We actually have more visibility into custom member statuses...
Marketo tends to miss business justifications for some features. With a little work on features like this, Marketo could easily obviate the need for overlapping or competitive products that do lead routing. The flexibility of smart lists and segmentations, combined with the visual interface for stri...
And ... one thing to note here, lest it be forgotten. This isn't an idea for a product feature or even an enhancement. This is one way to fix a bug that makes a very fundamental feature unusable for large enterprises.
This would make doing detailed troubleshooting so much easier.
Yup ... just went through it again and voted up some more painful and frustrating issues. Thanks for so diligently curating this list!
Agree. Here's the key point: To be an enterprise-class solution, Marketo has to enable change and growth. Even the best-planned integration will need updating as business requirements are refined. I get that mapping database fields at this "metal against metal" integration point is complicated. But ...