I'm trying to enable the Data Sync for the Salesforce integration, but keep getting this error: Unable to create Salesforce Pushtopic. Review Salesforce API settings.
I have set up the integration, I've also checked that the profile of the user who connected the integration has the permissions listed in this article: Zendesk for Salesforce integration - required profile permissions.
If the permissions are correct, one potential cause of this issue is that the account does not have enough available push topics to create one for the sync.
Different Salesforce plans have different allocations of push topics as described in the Salesforce developer documentation.
To check on how many push topics already exist, you can execute the following query in the SFDC Developer Console:
SELECT count() from PushTopic
If you're already at the limit for your SFDC plan, you'll need to free up some available push topics either by upgrading your plan or removing some of the others.
Another potential cause is when an disallowed field-type is used in the Sync Filter criteria:
Per our data sync documentation, the following field-types aren't allowed for filtering.
- Lookup Fields
- Formula Fields
- Long Text Area fields
The inability to use these fields is due to limitations in the SFDC Streaming API.
I am receiving a similar error just for the Contact sync "Unable to update Salesforce PushTopic. Review Salesforce API settings."
I have verified settings, in fact, it was once functional but now will not allow me to re-enable. Org and ticket sync are enabled and functioning. Any steps to try for this particular message?
There's a few reasons this could be happening. The fastest way to determine the cause of this would likely be on a screen-sharing session. I'll take a look to see if you've already got a ticket on this matter and get one started if you don't yet have one.
@... I am running into the same issue. My count in SF shows as 7. How many are needed for just the account to org sync?
It looks like you're already working with someone on this matter within a ticket. If there are findings from that ticket that have a broader application, we can post them here after it's been resolved.
Hi Dwight Bussman, we have the same problem as here:
Reconnection is not possible. Do you have a solution?
Hi Maik Künnemann
This will likely require a ticket with our Support Team to look more closely into this matter. Please contact support to start that process. Please reference this thread when you reach out so we have all the relevant information to get started.
How can I solved the issue regarding on unable to read salesforce push topic?
HeyO ken jon tarnate
This issue can be caused by a few different factors. If the steps listed in this article aren't helping to resolve this, I recommend reaching out to our support team so that we can take a closer look at your specific case.
This may hopefully help someone.
I have been battling this problem for months now and just realised that the field I was using as a condition in my sync filtering filter was a look up field, which the Zendesk Integration doesn't support.
It wasn't immediately obvious that it was a lookup field (I'd thought it was a pick list) so If you are still having trouble with this I would suggest looking through the fields you want to use one by one to make sure they are all supported types.
Here is the part in the configuration guide where it specifies which field types can be used.
Good callout. Thanks Nicole!
I was able to get it fixed by disconnecting and reconnecting the Salesforce integration.
It is frustrating that the integration breaks from time to time, and I am not getting any notification about it.
Our connection fails every now and then without any notification from what I can tell. Also had luck disconnecting and reconnecting in the past, but those steps are not working now. So I need to investigate more and/or enter a support ticket.
It looks like you have a ticket open with our Customer Care team related to this issue. They will continue troubleshooting with you to see why this issue is occurring on your account.
Thanks for bringing this to our attention!
Please sign in to leave a comment.