Service Issues

Report any Haven OnDemand API service issues to the development team here. Before submitting your issue and for issue status definitions, be sure to read this page.
Search the Dev Community
Showing results for 
Search instead for 
Do you mean 
0 Likes
Status:
Not an Issue

Why does it say Index Name invalid for some of the Requests - AddtoTextIndex

Status:
Not an Issue
by logontokartik Level 1 on ‎07-07-2014 02:21 - last edited on ‎07-07-2014 08:04 by Level 7

Hi,

For some requests its successful, but for some of the addtotextindex requests it says Index name invalid and returns 8002. Why does it do that? Below is one of the requests that failed.

 

https://api.idolondemand.com/1/api/sync/addtotextindex/v1?index=sfdc_idol_index&json=%7B%22documents... Method=GET]

 

 

{
  "error": 8002,
  "reason": "Job actions failed",
  "actions": [
    {
      "status": "failed",
      "action": "addtotextindex",
      "version": "v1",
      "errors": [
        {
          "error": 8002,
          "reason": "Index name invalid"
        }
      ]
    }
  ],
  "jobID": "usw3p_d564bc60-ee13-406a-a81c-c704aee704e0",
  "status": "failed"
}
Status:
Not an Issue
The reason this specific request fails is due to an invalid index name. The api-key is associated with a different index name as specified. I.e. the api-key and the current request are using sfdc_idol_index whilst the api-key is associaed with an index created called – kindex9
Comments
by Level 7
on ‎07-07-2014 08:06
Status changed to: Not an Issue
The reason this specific request fails is due to an invalid index name. The api-key is associated with a different index name as specified. I.e. the api-key and the current request are using sfdc_idol_index whilst the api-key is associaed with an index created called – kindex9
by hdas New Member
on ‎07-12-2014 03:46

But how a text index is related to API key ? There could be only one text index per account. It is not at all related to API key.

Social Media
† The opinions expressed above are the personal opinions of the authors, not of HPE. By using this site, you accept the Terms of Use and Rules of Participation