<aside>

Description

Per environment rules that prevent specific Salesforce metadata fields from entering the translation workflow. Each connected Salesforce org keeps its own independent rule set, with a master Active toggle that disables every rule without removing them.

</aside>

Prerequisites

• A connected Salesforce org. Create Salesforce Org Credentials

What this feature does

Exclude Metadata applies user defined rules during the metadata retrieve phase. Matching fields are skipped before any data is written to SimpleTranslate, so excluded items never appear in translation queues, never consume translation credits, and never affect progress statistics.

Common scenarios that the feature addresses:

• Internal API names that should never be localized, such as IPC_OrderManagement or SF_InternalRef.
• Third party managed package fields that already ship with their own translations.
• System fields that depend on stable labels.
• Fields owned by packages that maintain a separate translation pipeline.

Rule types

Two rule types are supported. Rules can be combined freely within the same environment.

Prefix (API Name)

A regular expression matched against the field API name. Example: ABC_* excludes ABC_CustomField__c and any other field with an API name that starts with ABC_.

Namespace

A literal namespace prefix matched against the field namespace. Example: SimpleT__c excludes Object_SimpleT__c and every other field that belongs to that namespace.

Rules are evaluated against both the direct field API name and the parent metadata API name, so namespace rules also catch nested fields inside larger metadata containers.

Open the Metadata Blacklist dialog

1. Open the Org Credentials section from the navigation bar.

2. Locate the target environment in the credentials table.

3. Open the environment action menu.

   

4. Select Metadata Blacklist.

Add a rule

1. Select Add Rule in the dialog.
2. Choose the rule type: Prefix (API Name) or Namespace.
3. Enter the pattern. Example placeholders guide each type: ABC_* for Prefix, SimpleT__c for Namespace.
4. Confirm that the validation feedback indicates a valid pattern.
5. Select Save to persist the rule set.

Edit a rule

1. Double click any rule row to enter inline edit mode.
2. Update the rule type or pattern.
3. Select Save to persist the change.

Delete a rule

1. Select the delete control on the target rule row.
2. Select Save to persist the change.

Activate or deactivate the rule set

The dialog footer contains an Active toggle that controls the entire rule set for the environment.

• Set the toggle to Active to apply every rule during retrieve.
• Set the toggle to Inactive to retrieve all metadata without applying any rule. The rules are preserved and can be re enabled at any time.

What to expect

• Validation runs on both the client and the server. Invalid regular expressions are rejected before save, not during retrieval.
• Rules are pre compiled at retrieve time, so retrieves over large metadata sets remain performant.
• Rules are scoped to a single environment. A rule on a Sandbox credential does not affect a Production credential.
• Excluded fields produce no skipped markers, no error log entries, and no UI noise. The translation queue only contains fields that match the active rule set.
• The Save button stays disabled until changes are made. New and edited rules remain visually highlighted until they are saved.

Common use cases

• Exclude an entire managed package, such as Conga, Veeva, or nCino, with a single Namespace rule for the package namespace.
• Exclude every internal field that follows a naming convention, such as INT_.*, with a single Prefix rule.
• Apply temporary rules during a migration and remove them once the migration is complete.
• Maintain different rule sets for Dev, UAT, and Production environments. Each environment keeps its own independent configuration.

Tips

• Test new regular expressions on a small set of metadata before applying them to a Production environment.
• Use Namespace rules for managed packages and Prefix rules for ad hoc patterns owned by your team.
• Use the Active toggle to temporarily include all metadata for an audit without losing the existing rule set.

<aside>

Quick View

End User Documentation

• SimpleTranslate
• SimpleT AI
• Organization </aside>