Knowledgebase

Sort by:
Issue When a Marketo field is synced to a SFDC field with a picklist, that picklist will be synced to Marketo when the field is added to a Marketo form. The values section of the field in the form will show the values from SFDC. However this does not occur with the standard state field in Marketo. Solution The state field's form picklist is not updated because it is automatically populated with the 50 US states.  To get around this, you can either manually update the values in the picklist in the form, or you can use a custom Marketo field. This field can be remapped to the state field in salesforce with assistance from support.
View full article
Issue When using the Filter 'Member of SFDC Campaign' in the Smart List and checking the people tab to see which records are qualified, this message occurs: Could not evaluate rule 1 (SFDC Campaign 'Campaign Name' not found) Note: it may state could not evaluate rule # - # can be any number, if the filter is number 5.  # will equal 5   Solution The Fix Ensure the that the SFDC Campaign being referenced in the Smart List is an ACTIVE campaign The Why This error occurs due to the SFDC Campaign not being an active campaign in SFDC. You may be wondering "Then why can I select the SFDC campaign in the drop down?" This is because the Smart List Filter specifically 'Member of SFDC Campaign' similar to 'Has Opportunity' filter reference a backend table in Marketo. This backend table is updated when a SFDC Campaign is removed or renamed. Therefore, Marketo does not directly perform an API call to check if the campaign is selectable, but rather uses the backend table as reference. One way to check in Marketo if the SFDC Campaign is active is to check the 'Added to SFDC Campaign' Trigger in a Smart Campaign's Smart List as that dropdown will only show active campaigns.  
View full article
Issue You would like to use the 'SFDC Oppty Campaign ID' as a constraint for the Smart List filters ' Has Opportunity' and 'Opportunity was Updated', however, it does not appear as an option. Solution By system design, there are some opportunity fields such as 'SFDC Oppty Campaign ID' that are restricted and cannot be made visible in Marketo as a constraint or filter. One workaround is to create a custom field in Salesforce on the Opportunity object that holds the same value as the 'SFDC Optty Campaign ID' field. As a result, this field will appear in Field Management and become visible as a smart list constraint or filter in Marketo. If you would like to implement this, reach out to your SFDC admin.      
View full article
Issue When trying to sync a lead to SFDC, it fails with an error message "_createSObjects failed - AgreementTaskTrigger: execution of BeforeInsert caused by: System.NoAccessException: Script-thrown exception ()" Solution Your Salesforce instance has a custom  SFDC trigger that fires when you create a lead in SFDC (in the example, the trigger is named "AgreementTaskTrigger") but the trigger was not able to execute, so the sync failed.  To investigate this, you will have to set up a debug log on the Marketo sync user in SFDC and have your SFDC admin look into the details. If you disable the trigger in SFDC, the sync will work without an issue.  
View full article
Included in this article Overview Use Sync User Login Check Field Level Security Overview If you've ever had trouble getting a field or field value to sync between Salesforce and Marketo, the most common problem is that the Salesforce sync user doesn't have permissions to access that field.   Since different users have different permissions to access fields based on their roles, not every field or record is visible to every user. However, there can be cases when a user needs access to fields which are not accessible. For example, if a program needs to be tested but the field is not accessible, or the user may have been simply missed from the permissions. In such cases, you can check whether the sync user can see that field.     Use Sync User Login To find if your sync user has permissions to access the field, check the Salesforce integration ID. Navigate to Admin > Salesforce and check the Credentials. This will give you the login ID. Your Salesforce Admin should have the password for that login ID.       Next, log into your CRM using those SFDC sync user credentials.       Navigate to the lead/contact record.       Check to see if the field shows on the lead record. If the field is not visible, that means that your sync user does not have permissions enable to access that field.       Check Field Level Security If the field isn't visible, we need to check the Field Level Security for the fields. This is where the fields will be listed with checkboxes indicating whether the field is to be accessible or not.   1. Go to Setup.       2. Navigate to your Profile.       3. Go to the section “Field Permissions.”     Here you’ll be able to see the fields and their corresponding permissions. Restricted permissions could be a reason why the SFDC sync user cannot see a field or record. Therefore, you may need to make changes here to allow permissions to view it.
View full article
Issue Lead owners are required when syncing a lead to Salesforce, but is there a way we can sync them without assigning a lead owner? Yes there is, and it's called lead queues!     Solution How to do it: Lead queues must be set up in Salesforce first. Like lead owners, the queues must be visible to the Marketo Sync user before they can be selected. Select the lead queue you want leads to be assigned to in the 'Sync Lead to SFDC' or 'Change Lead Owner' flow steps. Qualified leads that pass through this flow step with then be synced to Salesforce and assigned to the lead queue rather than a lead owner. A few important notes: Only leads can be assigned to a lead queue, contacts cannot and must be assigned an owner. Assignment rules in Salesforce can conflict with the request sent from Marketo. Double check these assignment rules to make sure there are no conflicts.  
View full article
Issue When using the "Sync to Salesforce" flow step and setting up choices, selecting "Do Nothing" uses the Auto-Assignment Rules in Salesforce. Solution This is expected. For this flow step, the choices are basically asking whether the record should be assigned to a specific person or not. When it is not specified (i.e., "Do nothing") the assumption is that you still want the record to be synced to Salesforce, otherwise they would not be in that step, but that there's no particular desire to assign it to a specific person. Thus, since SFDC records need someone to be the owner, the Auto-Assign rules are used by default  
View full article
Issue When creating a Smart List with a "Member of SFDC Campaign" filter, the SFDC Campaign is visible on the drop-down list, yet it throws an error when selected and the Smart List is loaded: "Error running Smart List: Check your Smart List configuration" Solution Things to check: The campaign has been re-named in SFDC or has been deleted. It could also be that somehow a "space" has been entered before the campaign name. For example, Marketo is looking for "SFDC Campaign Name" and SFDC has it as " SFDC Campaign Name" or "SFDC Campaign Name ". The campaign is present and active in SFDC, but is not visible to the sync user. The Marketo Sync User details can be located in [Admin > Integration > Salesforce > Username] This can be checked by logging in to SFDC as the Marketo sync user and verify that the campaigns are present with the correct name and activated for that sync user.    
View full article
To ensure all your activities show up under the Activity History (as opposed to Open Activities) make sure you have a "Completed" values in the Task Status list and that it's a "Closed" state. Here is how to check it:   In SFDC, go to Setup > App Setup > Customize > Activities > Task Field.  Click on Status In the Task Status Picklist Values list, check if you have a "Completed" value.  If you do have it, skip to step 5. You need to create the "Completed" value.  Click on the New button Type in Completed and click on Save Click the Edit link next to the Completed value Check the box next to Closed and click on Save. Once the steps above are completed, you should now Completed in the list with "Closed" checked like this:    
View full article
Issue Salesforce is going to change your instance sub-domain from NA#1.salesforce.com to NA#2.salesforce.com. What measures should you take in order to make sure that our sync works? Solution Marketo accesses SFDC with the API login endpoint, so a change in the login domain that you use would not affect the Sync user. Marketo and SFDC sync should continue to work irrespective what domain SFDC belongs to. If a change happened to SFDC that affected the sync user, such as its credentials or the SFDC OrgID changed, then Marketo would need to be updated If there is an issue with your sync after updating the SFDC domain, try the following to resolve the issuce. Change your SFDC Sync User's password. Issue a new security token. Re-enter the credentials within Marketo Admin >Salesforce. If it doesnt resolve the sync issue, contact Marketo support and they will be able to help you out.    
View full article
Issue When you use the "Add to SFDC Campaign" flow step, and the lead isn't already in SFDC, this step will sync the lead to SFDC, and you want to know which assignment rules will be applied.   Solution The SFDC auto-assignment rule will be used. To explain this further, if for some reason you don't have lead assignment rules firing properly in Salesforce, it will be assigned to what is called the "Default Lead Owner" in Salesforce. It's not just "Add to Salesforce Campaign" that uses what is called "implied Salesforce actions". All of the following flow steps will sync the lead to Salesforce first before running the flow step if the person is not already synced to Salesforce: Add to Salesforce Campaign Change Status in Salesforce Campaign (this will sync them AND add them to the campaign first) Change Owner Convert Person Create Task      
View full article
Issue Change Lead Owner reason shows "Synched from salesforce.com - fixup Lead Owner." Solution The "synched from salesforce.com fixup lead owner" activity means the lead owner was switched within SFDC, often times through auto-assignment rules. The phrase "fixup Lead Owner" is what Marketo records when it is taking the Owner ID being passed from Salesforce and translating it into the Lead Owner values (First Name, Last Name, Email Address, etc) to populate into Marketo.
View full article
Issue Change Lead Owner reason shows "Synched from salesforce.com - fixup Lead Owner." Solution The "synched from salesforce.com fixup lead owner" activity means the lead owner was switched within SFDC, often times through auto-assignment rules. The phrase "fixup Lead Owner" is what Marketo records when it is taking the Owner ID being passed from Salesforce and translating it into the Lead Owner values (First Name, Last Name, Email Address, etc) to populate into Marketo.
View full article
Issue Activity History in Saleforce shows this message: [Email details are being uploaded from Marketo...please check back later] when emails are sent out from the Marketo Outlook Plugin.     Solution This message is created because of insufficient privileges for the Marketo sync user inside of SFDC. There is a permission for “Edit HTML Templates” that needs to be enabled for the sync user in order to prevent this problem from occurring. Background: When you send an email using the Marketo Outlook plugin, it is sent through the user's Exchange server rather than Marketo's email servers. Many users have an email signature that is automatically added to the email. This adds additional HTML to the email, which does not match the template already in Salesforce Sales Insight. Normally, Marketo would create a new template which Salesforce could then display in a link in the Activity History. However, in this case, the Marketo sync user does not have the necessary permissions, so this error results. To fix this, enable the "Edit HTML Templates" permissions to your Marketo Sync User.   Who This Solution Applies To Customer who are using Sales Insight for Salesforce and Outlook    
View full article
Issue The SFDC sync error "Unable to process due to no XML response from Salesforce" appears. Root Cause This error means Marketo received an invalid XML response returned by SFDC. Most often, this is a transient error from SFDC and resolves on its own in the next sync cycles.  If the error persists or is continually blocking your sync, please reach out to Marketo Support.
View full article