> 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/why-is-my-form-response-not-properly-created.md).
# Why is my Form Response not properly created?
If you submitted a Form Response and it was not created on Salesforce, or it was created with missing related Form Answers, follow the steps below.
* Make sure that your API user has the "SharinPix Form" permission.
{% hint style="info" %}
The API user is the same user who granted SharinPix with full access to your Salesforce from the SharinPix Settings page.
{% endhint %}
* Check if there are any errors in the "Error Messages" field on the Form Response record if it was created.
* If nothing is present, check for errors in the SharinPix back office.
* Go to the "SharinPix Settings" page.
* Click on "Go to Administrative Dashboard".
* Click on the "Form Responses" tab.
* Click on the "Record Not Created" tab.
* Click on the first Form Response and check for error messages in the "Message" row.
If the error does not appear to be an issue or requires no further action, click **Upsert on Salesforce** to retry.
| Options | Description |
| ------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Resync the Salesforce record fields when upserting the form response. | Select this option if you want your configured fields are synced with your response again. |
| Recreate the related Salesforce records when upserting the form response. |
Select this option if you want the child records to be recreated.
Note: Recreating related Salesforce records duplicates any previously processed records.
|
{% hint style="warning" %}
*The **Upsert operation in Salesforce** may not function properly if the associated Form Template Version is misconfigured. It can also be affected by other factors, such as outdated field mappings caused by changes you made to the Salesforce schema, or insufficient object and field permissions.*\
\
*For more information on Form Template Version, you can refer to this documentation:*\
[SharinPix Form Template Editor](/forms/form-elements/sharinpix-form-template-editor.md)
{% endhint %}
To prevent future errors, ensure the Form Template mappings are updated whenever your Salesforce schema is modified and make sure the appropriate Form Template Version is activated. If the error persists, contact the SharinPix Support team at [**support@sharinpix.com**](mailto:support@sharinpix.com)**.**
---
# 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/why-is-my-form-response-not-properly-created.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.
