SalesInsight 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.

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.



In the ServiceNow navigation bar, navigate to Perspectium > Control and Configuration > Properties. This will open up the Perspectium Properties page. Scroll to the bottom of this page to find your current Perspectium Update Set Version.

Records that exceed either ServiceNow or Perspectium's record size limit cannot be bulk or dynamic shared out. To check which records or fields are too large to send, log into the ServiceNow instance you are trying to share from and navigate to Perspectium > Logs. For any records that are too large to bulk/dynamic share out, you will see an error message indicating the record size limit that was exceeded as well as any fields that were notably large.

For tables that have HTML fields, such as the Knowledge (kb_knowledge) table and its text field, use the encrypted_multibyte encryption mode to ensure the HTML fields are sent out properly.

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)?

By default, dynamic shares will share records for the table you select as well as any associated child table records for that table. However, if you want to dynamic share only the records for the table you have selected in the dynamic share form, you can make use of the Share base table only checkbox under Trigger Conditions.

By checking the Share base table only box, child records associated with your selected table will not be dynamic shared out to your subscribing instances. Only the records for the “base table” (table selected from the Table dropdown in the dynamic share) will be dynamic shared. For more information, see share base table records only.

By default, your ServiceNow instance will encrypt messages by using the encryption key in your Replicator Properties. However, if you want to use a different encryption key for each instance, you can go into your Shared Queues and enter your record encryption key for each shared queue.

The role perspectium_readonly can be assigned to any users accessing your ServiceNow instance. Assigning the perspectium_readonly role will restrict Perspectium Replicator for ServiceNow functionality so that users cannot delete, modify, or create new records for the following:

  • Shared/Subscribed Queues

  • Bulk/Scheduled Bulk/Dynamic Shares

  • Table/Transform Maps

  • Perspectium Properties

To assign the perspectium_readonly role to a user in your ServiceNow instance, follow these steps:

  1. Log into your ServiceNow instance as a System Administrator.

  2. In the top left navigation window, type User Administration and then navigate to User Administration > Users

  3. Click into the user whose role you want to change. Then, scroll down to the bottom of the User form and click the Edit button under the Roles tab.

  4. In the left side search window under Collection, type perspectium_readonly. Then, select the perspectium_readonly role and move it to the Roles List by clicking >. Finally, click Save.




Similar topics


Contact Perspectium Support


US: 1 888 620 8880

UK: 44 208 068 5953

support@perspectium.com