Using it in the ERD
Once the pin is in place, typing a column logical name fills in the physical name and the domain. This page separates what happens automatically from what still needs your decision.
From logical name to physical name
Type into the logical name cell in the table detail or the column grid, and the physical name assembled by the dictionary goes into the column name. Letter case follows the DBMS policy, so the result matches what you would have typed by hand.

If a column with that name already exists, the physical name is left alone and the reason is reported.
Applying and suggesting domains
The domain is decided from the trailing word of the combination. Whether it is applied depends on how many candidates there are.
- With exactly one candidate it is assigned immediately.
- With more than one it is only suggested. The suggestion is highlighted at the top of the domain picker and the default stays unassigned.
- When auto increment conflicts, only that field is dropped and the rest of the attributes are applied. Most engines allow one auto increment column per table.
- Editing a value the domain governs releases that column from the domain.
Columns that need review
Open needs review from the logical name cell menu to see everything flagged on that column in one table.
| Item | Meaning |
|---|---|
| Unregistered | Part of the logical name could not be read by the dictionary. |
| Out of step | The name the dictionary would build differs from the current physical name. |
| Related word | Another word is used for the same meaning. |
| Antonym | The paired column can be created. |

If the logical name contains a synonym or a forbidden word, standardize rewrites the logical name itself with the standard words. Dictionary trace shows which range was read as which word.
A column that does not need the related-word hint can hide it for that column only.
Registering an unknown word
On a range that could not be read, register word lets you enter the word and its abbreviation right there and recombines immediately. The registration is scoped to that connection, so the source dictionary is untouched.
- An abbreviation already in use is rejected.
- If the spelling already reads as a synonym or a forbidden word of another word, you are told and left to decide.
- The remaining fields such as description, synonyms and antonyms can be filled in later in the dictionary editor.
Renaming a column that already exists
A column that already exists in the database is never renamed or retyped automatically when you add a logical name. Documenting a table should not silently create pending changes.
When the name the dictionary would build differs from the current physical name, the logical name turns italic and a regenerate icon appears on hover. The tooltip shows the new name and warns that a pending change will be created first, so the click is the answer.
The domain only goes as far as a suggestion here. Agreeing to a rename is not agreeing to a type change.
Antonym pair columns
When the word has an antonym registered, the paired column can be added in one step, with abbreviation, domain and nullability mirrored.
Table names work the same way
A table logical name builds a table name the same way. The database COMMENT, however, is left untouched.
Logical and physical display modes
Switch the ERD between logical and physical names. The mode carries into image export, embeds and shared snapshots, so there is no need to draw one diagram for business review and another for development.

Logical mode works best together with a data dictionary, since a column with no logical name has nothing to show.