> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/ncino/feature-deployment/field-exclusion-settings.md).

# Field Exclusion Settings

**Configure Excluded Fields in Deployment**

Excluded fields control which object fields are omitted from deployment processing. This guide explains how field exclusions are reviewed during Deployment setup, how predefined audit field exclusions appear in the workflow, and how the same exclusions are confirmed before deployment execution.

## Before starting

The deployment workflow is already in progress and the Destination step is active. Source type and Source are complete, Deploy to is enabled, and the destination organization is selected. Commit settings are available when Commit to is enabled.

* A Destination org is selected.
* Commit settings are configured when the deployment also commits changes.
* A template or source configuration is selected for the deployment.
* The object mapping table displays the objects included in the selected configuration.

![](/files/880161af153a6a957282ea7dc5593c30a3fb8479)

## Review the applied filter

The Applied filters column provides access to the filter configured for an object mapping. Opening the filter displays the configured record-selection criteria for the selected object.

![](/files/8bfbc2e3ea535f0c5c90abfe5e858dffb6658da1)

After the filter is reviewed, the workflow returns to the Destination step. The object mapping table remains available for reviewing external ID mappings, sorting criteria, applied filters, and excluded fields.

![](/files/1765505b2ff8476293e129e86d1ef2cf84787d67)

## Review excluded fields for an object

In the Excluded fields column, opening Exclude fields displays the Field Exclusion Settings panel for the selected object.

![](/files/6a63657f98f4abc5a6385a9fe1a6def9d71170d2)

The panel opens in All Fields view and indicates the number of fields currently excluded for the selected object. Excluded fields are selected in the list. Audit fields such as CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, LastViewedDate, and LastReferencedDate are excluded by default.

\*\*Note:\*\*Audit fields are excluded by default to maintain data integrity and comply with organizational policies. These excluded fields may appear in downloaded results, but those are not considered for deployment.

## Filter the field list

The Field Exclusion Settings panel includes a list filter for switching between field views. The available views are Show all fields, Show only excluded fields, and Show only mandatory fields.

![](/files/171864e2f3bf657c5699bbf8a880e2a7e0b07740)

**Field list view options:**

1. Show all fields keeps the complete field list visible.
2. Show only excluded fields narrows the panel to the fields currently excluded from deployment processing.
3. Show only mandatory fields checks for mandatory fields in the selected object context.

When Show only mandatory fields is selected and no matching fields are available, the panel displays No fields found. Returning to All Fields restores the complete field list for review.

![](/files/aa33b7382a54430af4e31d5ae81ff4ab5a0913c3)

![](/files/14f1bbf9bd45a7093fbbced2afea93f209bee0f9)

## Confirm excluded fields in Preview

The Preview step consolidates the deployment configuration before execution. Source details, Destination details, Job settings, and object mappings appear in a single review page.

![](/files/4461c60f6d69e3237883c0aa59ecf93b4c2705a8)

The Applied filters column confirms the configured object filter, and the Excluded fields column remains available for final review. Opening Excluded fields from Preview displays the exclusion details in read-only mode.

![](/files/6c247968294bd73ff9f50be25f1f3cb51aaa9e94)

Field Exclusion Settings (Readonly) confirms that the same audit fields are excluded for the selected object. The read-only state supports review without changing the finalized Preview configuration.


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/ncino/feature-deployment/field-exclusion-settings.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.