You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


General Issues

When configuring your Perspectium Properties for Salesforce, you may run into an issue where you are unable to save your properties. There are various possibilities that may be causing this issue.

Refer to the potential solutions below: 


Check your credentials 

  • Ensure that your password is correct for the user being used. 
  • Ensure that the entered security token belongs to the user being used. 

Check your Consumer Key and/or Consumer Secret

Ensure that the Salesforce Consumer Key and/or Salesforce Consumer Secret you are inputting do not contain white spaces. It is recommended to paste your keys to a text editor to ensure there are no white space. 

OAuth Endpoint 

OAuth Endpoint may vary depending on your environment. Here are the three OAuth Endpoints to try: 

  1. https://login.salesforce.com/services/oauth2/token
  2. https://<YOUR_SALESFORCE_ORG_HERE>.salesforce.com/services/oauth2/token (i.e., https://na112.salesforce.com/services/oauth2/token)
  3. https://test.salesforce.com/services/oauth2/token (ONLY for Sandbox org) 

Whitelist IP range

In your Salesforce, go to Setup on the top-right corner of the page. 

Go to Administer > Security Controls > Network Access, or simply type Network Access in the Quick Find / Search bar and click Network Access.

Click New. Then, fill in the required fields, Start IP Address and End IP Address, and click Save.



After modifying a Salesforce Apex trigger, there are several points you should check to ensure that data will be shared out of Salesforce properly:

Check that your Queue ID (2nd parameter in the pspOutMessage function) matches the Queue ID for the shared queue you created in Salesforce.

To locate the Queue ID for your shared queue in Salesforce Lightning, navigate to > Perspectium Replicator > Queues. Then, click the Queue Name of the shared queue whose ID you want to locate. On the resulting page, the shared queue's Queue ID will be the alphanumeric code displayed in the page URL immediately following /persp__PSPQueue__c/ and preceding /view.



To locate the Queue ID for your shared queue in Salesforce Classic, choose Perspectium Replicator from the dropdown in the uppermost right-hand corner of the screen. Then, click Queues and click the Queue Name of the shared queue whose ID you want to locate. On the resulting page, the shared queue's Queue ID will be the alphanumeric code displayed in the page URL immediately following /PSPQueue?id= and preceding &.

(info) NOTE: The Queue ID in Salesforce Lightning will be an 18-character code, while the Queue ID in Salesforce Classic will be a 15-character code.

Check that your triggerWhere variable's value is set to the correct Base64 encoded SOQL query. To Base64 encode/decode your SOQL query, see Base64 Decode and Encode.

If using a Queue Alias, check that the Queue Alias (2nd-to-last parameter in the pspOutMessage function) matches the Queue ID for the shared queue you created in Salesforce.


If you are seeing that you are not sending data out of your instance as fast as you would like, check the following information:

  • Is the count of my Outbound Messages [psp_out_message] consistently very high (+250k Ready Message)?

  • Is my property for maximum bytes per post too low (should be in the 5 MB to 10 MB range)?

  • Is my property for max record per post too low (should be around 2000-4000 records)?

  • How often is my Perspectium MultiOutput Processing job running (default to 30 seconds)?


Known Issues 

As of the Gold Release for DataSync for Salesforce, there is a known issue where the Perspectium Job in Salesforce continuously runs. A workaround to this issue is to leave the Description field blank when you create a Perspectium Job. Doing so will populate the Description field with the last scheduled run time. 


FAQs

If the number of Apex jobs scheduled in your Salesforce org exceeds the maximum number of allowed jobs, then those additional jobs that exceed the maximum will not run. The default value for the max Apex jobs in your Salesforce org is set to 5. This value is set in order to prevent Apex jobs from impacting the overall performance of your org. To change your max number of Apex jobs, navigate to Setup > Custom Settings > Manage ReplicatorJobSettings > Edit. For more information on Salesforce Apex job maximums and intervals, see change Salesforce job intervals.





Can't find what you're looking for?  

See the FAQ or browse the Perspectium Community Forum.



  • No labels