Forum Discussion
Hello again
It's still not very clear, and unfortunately I dont know how to explain it better but I can try and deepen my examples a little.
1. We're looking to implement Coveo as our search engine. One of the benefits (of many) with Coveo is that they can search across several repositories. Let's say that we're searching across the TKB, a SFdC repository and Youtube.
In this example, will ONE search result in ONE API call, or three?
2. Say that a portion of the user settings are on the Lithium Database, but another subset are tied to different areas of our backend SFdC database. Will an update in X amount of the SFdC (perhaps in different places within our SFdC instance) result in ONE call, or will it be several depending on where the information have to go in our SFdC instance?
3. If we implement the Case Portal functionality in Lithium and a user updates for example the license information in one table, the version number in another table and also putting in a comment in the case. In doing so it updates the status of the case in yet another table. All in SFdC. Is this ONE API call to salesforce, or several to all the different areas of our Salesforce instance.
Thanks again for your help, and sorry for being to thick headed :)
-Matt
Hey Matt,
Lithium's "Billable API calls" refer to any API calls made from an external party to a Lithium community.
1) Since Coveo is an external party, you would have to check with them about how many API calls they make to Lithium and when. If I recall correctly, I believe they used to use a crawler behind the scenes and then store the results which would not result in API calls getting incremented, but it's best to check with them.
Unfortunately, I'm not too familiar with our SFDC connector functionality, so I would have to defer to VimalGa for the other 2 questions.
Hope this helps,
Yuri
Related Content
- 8 months ago
- 10 months ago
- 2 years ago