> 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/documentation/features/search-images/your-salesforce-filters.md). # Your Salesforce Filters ## Why Affix Filters ? * The affix filters can prove to be useful in the event you are using special album IDs on Objects, for instance, an object that contains two albums with Ids **\\_Req** and **\\_Other** to distinguish between images that are required and other images irrelevant images respectively, you may make use of the Affixes section to filter those images from the Search results. ## How to define Affixes for SharinPix Search * Affixes are either prefixes or suffixes that are attached to Salesforce Object Ids retrieved from reports used for searching images. For instance, creating a prefix with value "**User\_** " and using it in search will perform a search on **IDs** prefixed with it, i.e, "0030Y00000AKAUl" will become "User\_0030Y00000AKAUl". * To create an affix: * In **Salesforce Classic Experience**: Go to **Setup** > **Build** > **Develop** >**Custom Metadata Types** * **In Salesforce Lightning Experience:** In the **Quick Find** box, enter **Custom Metadata Types** * Click on **Manage Records**, next to SharinPix Search Affix (as shown in the screenshot below).
* Click on **New** to create a new prefix or suffix. * The Label field is the text displayed on the SharinPix Image Search form; the Affix Type is whether the Affix Value entered should be prefixed (prepended) or suffixed (appended) to the ID. The Affix Type should either be "Prefix" or "Suffix". Affix Value is the actual value that is affixed to the ID; this will be used as is. * To set an initial value on the Search form, check or uncheck the **Initial value on SharinPix Search form**.
* Set the Affix Value as required. * Click on **Save** when you are done. --- # 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/documentation/features/search-images/your-salesforce-filters.md?ask=&goal= ``` `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.