> 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/best-practices/images-on-salesforce-report-and-views.md).

# Images on Salesforce Report and Views

To access SharinPix images in Salesforce report and Salesforce views you can either:

* rely on [SharinPix Image records](/documentation/image-sync/the-sharinpix-image-object.md) (which are automatically generated once you [setup SharinPix Image Sync](/documentation/image-sync/setup-sharinpix-image-sync.md))
* automatically populate your standard or custom object fields with images

![](/files/p4ZdbEqZQVn9jYDpNuTH)

To populate fields with images the easiest way is to use the [SharinPix Tag Action](/documentation/features/working-with-tags/tag-action.md) feature.

When applying a tag, an URL field can be automatically updated with an URL specifying a version of the image. This URL value can be [rendered in a Formula field](/documentation/cookbook/display-an-image-in-a-salesforce-field-using-tag-action.md) which can then be used elsewhere in Salesforce, such as in Views, Reports, Emails or Documents.

**Best Practice: you can rely on SharinPix Single Image to simplify the UI and the automation you need after uploads, including saving the Image in a field.**

As an example 4 different Single Image Components can be used to upload different car views (such as front, back, right and left). Each Single Image can be associated with a specific tag value (respectfully front, back, right, left) and fields can be populated accordingly (example: front URL, back URL, right URL and left URL). For each view, those URLs can be rendered in Formula fields (front image, back image, right image and left image).

Then, you just have to use the formula fields in a view to get an overview of the image taken by line of report very easily. This of course requires the usage of Tag Action for each tag.


---

# 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/best-practices/images-on-salesforce-report-and-views.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.