Attribute Technical Naming Convention
Specifies the technical naming convention used for attributes in your business model. Choose from predefined conventions like PascalCase, camelCase, UPPER_CASE, lower_case, etc.
Options: Inherit, None, PascalCase, camelCase, Proper_Case, Proper Case, UPPER_CASE, lower_case
| Option | Result for Order Date |
|---|---|
Inherit | Uses the Entity Technical Naming Convention instead |
None | Spaces are replaced with underscores (Order_Date) |
PascalCase (default) | OrderDate |
camelCase | orderDate |
Proper Case | Order Date |
Proper_Case | Order_Date |
UPPER_CASE | ORDER_DATE |
lower_case | order_date |
The convention is applied when an attribute's Technical Name is derived from its name in the Business Modeling editors. It is also used wherever BimlFlex derives a technical attribute name: the Integration Key attribute added for a business entity is named by applying this convention to the entity name and appending the Integration Key affix, and the Column editor derives a column's Business Name with it when no Business Attribute is linked.
When to Change This Setting
Keep the default PascalCase for compact technical names that translate directly into column names. Use Inherit to keep entity and attribute technical naming on a single convention, or pick the convention that matches your database naming standard.
Related Settings
| Setting | Interaction |
|---|---|
| Entity Technical Naming Convention | Used instead of this setting when the value is Inherit |
| Attribute Naming Convention | The equivalent convention for attribute display names |
| Append Integration Key | The affix combined with the formatted entity name for derived Integration Key attributes |
Notes
- This setting is part of the Model settings category.
- The default value for this setting is
PascalCase.