> 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-when-attempting-to-add-sharinpix-components-in-field-service-mobile-flow-what-should.md).

# I got an error when attempting to add SharinPix components in Field Service Mobile Flow. What should I do?

When attempting to use the following SharinPix components:

* SharinPix Map
* SharinPix Mobile Launcher
* SharinPix Related Search

in a **Field Service Mobile Flow**, the following error is presented:

![](/files/0WuTtUNvFjDt6X9uzohh)

![](/files/IgVSY9lae56iT9rgCspv)

The above components appear in a Field Service Mobile Flow but, are inoperative in this type of flow.

However, the behaviour of the **SharinPix Mobile Launcher** component can be replicated by making use of a Field Service Mobile Flow that integrates a SharinPix deeplink URL to launch the SharinPix mobile app. For more details on how to make this integration, refer to the following article:

[Integration of SharinPix App with SFS (FSL) App using Flows](/documentation/integrations/salesforce-field-service/integration-of-sharinpix-app-with-sfs-fsl-app-using-flows.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sharinpix.com/faqs/i-got-an-error-when-attempting-to-add-sharinpix-components-in-field-service-mobile-flow-what-should.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.