You are here:
Flexcard Naming Conventions (Managed Package)
For the managed package runtime, follow requirements when naming Flexcards and Flexcard elements to prevent errors when working with the Flexcard Designer and importing Flexcards as datapacks. For example, you may run into issues when importing a Flexcard with the same name as one that already exists in your org.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Flexcard Naming Requirements
Requirements |
Examples |
|---|---|
The combination of the card Name and Author must be unique in your Org. For example, if importing a Flexcard with the same name and author of a current Flexcard, you will be asked if you want overwrite the current Flexcard in your org. |
|
The name and author must only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. |
Not acceptable:
|
If you have multiple versions of a Flexcard, only one version can be active at a time. See Flexcards Versioning (Managed Package). |
N/A |
Flexcard names cannot be changed. You must clone a Flexcard to change the name. See Clone a Flexcard. |
N/A |
Flexcard Element Name Requirements
Requirement |
Examples |
|---|---|
|
Acceptable:
Not acceptable:
|
