> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/faqs/i-got-an-error-visit-id-value-of-incorrect-type-sharinpix-visit-c-what-should-i-do.md).
# I got an error 'Visit: id value of incorrect type: \[sharinpix\_\_Visit\_\_c]. What should I do?
If you encounter an error message similar to: `Upsert failed. First exception on row 0; first error: FIELD_INTEGRITY_EXCEPTION, Visit: id value of incorrect type: : [sharinpix__Visit__c]` or if the image sync feature is not working as expected on the Visit object, this may be due to a mismatch between the standard Salesforce Visit object and the SharinPix Visit object.
Such mismatch usually occurs when the fields with the same API name exist on both the standard and SharinPix Visit objects.
For example, having Visit\_\_c on the standard object and sharinpix\_\_Visit\_\_c on the SharinPix Visit object may cause a mismatch in the image sync configuration.
Kindly note that in such cases, the **sharinpix** namespace is ignored.
To avoid such mismatch, ensure that no two field API names are added on both objects. In image sync configurations, for instance, this can be done by changing the field API names on the SharinPix Visit object so as it doesn't match any existing field API names on the standard Visit object.
{% hint style="success" %}
**Tip:**
If the issue still persists after applying the above workaround or if you need further assistance to resolve such issue, kindly contact SharinPix support on ****.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sharinpix.com/faqs/i-got-an-error-visit-id-value-of-incorrect-type-sharinpix-visit-c-what-should-i-do.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.