> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/actions/data-conversion-and-formatting/format-text-in-sobject-collection.md).

# Format Text in SObject Collection

## Overview

This action allows you to easily change the format of a text field within a collection of Salesforce records (SObjects). You can apply various formatting operations, such as capitalization, camel case, or escaping special characters for different contexts (like CSV or HTML).

## How it Helps

Imagine you have a collection of Leads with inconsistent capitalization in the "Company" field. This action lets you quickly standardize the format of those company names, ensuring consistency and improving data quality.

***

## When to Use It

This action is ideal for:

* **Standardizing text formats within your records.**
* **Cleaning up data for consistency and presentation.**
* **Preparing data for integration with other systems or components.**
* **Automating text formatting tasks within your flows.**

***

## Example

To format Contact names with proper capitalization:

1. **Retrieve Contacts:** Use a "Get Records" element to fetch a collection of Contact records.
2. **Configure the Action:** Select the Contact collection, specify "FirstName" as the field name, and choose "Capitalize" as the operation to ensure that all first names start with a capital letter.

***

## Key Considerations

* **Source Collection:** Ensure you have a valid collection of SObjects.
* **Field Name:** Choose the text field you want to format.
* **Operation:** Select the desired formatting operation (e.g., capitalize, camel case, escape HTML)


---

# 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.avonnicomponents.com/flow/actions/data-conversion-and-formatting/format-text-in-sobject-collection.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.