Kenny_Elkington

Hey Amy,The Modeler requires that leads move into the known stage prior to moving to a further stage, so you will need to account for this in your lifecycle.

Hi Robby,Are you sending this as a test email? If so, there would not be a lead to populate the email address from. Try using a sample lead, and it should pull the address from the selected record.

You can do it, Mary. I've beaten Josh on points at least three weeks this year, so the dream is alive.

Hi Dory,It's extremely rare that Marketo would make concurrent attempts to access the same record or a record and its parent at the same time, so I don't belive that this could be a result of something changing on the Marketo side. If you have seen performance degaradations in SFDC it's possible th...

Hey Rasmus,I'd suggest using the whenReady callback instead, as it waits until the form is completely done loading likie this:MktoForms2.whenReady( function(form){$('#mktoForms2BaseStyle').remove(); $('#mktoForms2ThemeStyle').remove();});

Hey Runn,It looks like your root URL isn't correct, "//app-sjst.marketo.com". You'll want to change 'sjst' to whatever is in your URL when you login to your Marketo subscription, like 'ab05' or 'sjn'.

Hey Val and Elena,This indicates that when attempting to write to a record it is already being written or locked by another record. You can find more extensive explanations here: http://salesforce.stackexchange.com/questions/27093/salesforce-parent-locking-unable-to-lock-row https://developer.sales...

Hey Matt,Sorry I didn't get back to you sooner. This doesn't look right, can you log a support case with the info which you've provided here and an example lead and landing page where you've seen this occurring?

From a posting I made in this discussion: https://community.marketo.com/MarketoDiscussionDetail?id=90650000000PmVNAA0It's likely that the Record Type ID is not a valid record type for the particular object which is being synched. For example, if I assign a Lead record type to a Contact in MArketo, ...

Hey Ben,What's you're reasoning for doing this client-side? Exposing the access token to be client-facing opens you up to some serious security issues. You should really only be executing this from the server side, and then sending any relevant data to the client with your page load.