You are here:
Object and Field Alias Considerations
Let’s look at some points to consider when you create, modify, or delete object and field aliases.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled |
- You can create field aliases for source fields only if you have access to the underlying source object to which the source field belongs.
- You can’t modify or delete a field alias that’s used in an active expression set.
- You can modify the source field of a field alias only if the field alias isn’t used in an expression set version.https://help.salesforce.com/s/articleView?id=ind.netzero_outcome_management_setup.htm&type=5&language=en_US
- You can modify the source field for a field alias that’s used in an inactive expression set
version if:
- The source field belongs to the same source object that's used to create the field alias.
- The data type of the source field is unchanged.
- You can’t modify the usage type of a field alias after the alias is created.
- Reference fields that point to multiple objects or do not point to any valid sObjects are not supported.
- Compound fields are not supported.
- The following field types are supported as field aliases:
- PERCENT
- CURRENCY
- NUMERIC
- INTEGER
- LONG
- DOUBLE
- INT
- DATE
- DATEONLY
- BIRTHDAY
- DUEDATE
- BOOLEAN
- AUTONUMBER
- STATICENUM
- DYNAMICENUM
- RECORDTYPE
- PHONE
- FAX
- ENUMORID
- URL
- ADDRESSCOUNTRY
- ADDRESSSTATE
- CURRENCYCODE
- MULTILINETEXT
- TEXT
- TEXTAREA
- PICKLIST
- STRING
- ENTITYID
- PERSONNAME
- SWITCHABLE_PERSONNAME
Did this article solve your issue?
Let us know so we can improve!
