Pinning to a connection
Choose which connection uses which domain and dictionary. This page covers pinning, version locking, and edits that apply to one connection only.
Pinning a domain and a dictionary
Right-click the connection to open its settings and go to the Data Dictionary tab. There is a domain slot and a dictionary slot, both optional. An empty slot simply means the feature is not in use.
- Use the slot button to pick an asset and the published version to use.
- An asset with no published version cannot be pinned. Publish it from the asset screen first.
- Changes take effect only after you press Save.
If the dictionary you picked pins a domain pack, the domain slot is locked to that pack and shows a from dictionary badge. To choose a domain separately, change or remove the dictionary.
Version locking and new version alerts
A pin points at one version. A newly published version is not picked up automatically; the slot simply shows a new version badge. Pick the version again in the slot to move up.
Following the latest automatically is deliberately avoided, so that a change in the standard is reviewed before it reaches your design.
The Data Dictionary node in the tree
Pinned slots appear as a Data Dictionary node under the connection. When both slots are empty the node is not drawn at all. Click the node to open the domains and words this connection actually uses.
Edits that apply to this connection only
Without cloning the whole pack, you can add, edit and remove domains and words for this connection alone. The source asset is untouched, and other connections using it are unaffected.
- The panel header shows how many entries were added, modified and removed.
- If the source changed after you pinned it, a source updated badge appears. Pulling the current contents keeps your connection-only edits.
- Pulling again discards edits you have not saved.
- A single entry can be put back with revert to pack.
Words you register on the spot in the ERD, when the dictionary could not read a term, also land in these connection-only edits.
Edited entries become available in the ERD and the table detail only after you save.
Unpinning and replacing
Unpinning a slot or swapping it for another asset also deletes the connection-only edits on that slot. For the domain slot, domains assigned to columns are released as well. The column values themselves, such as type and length, stay as they are.
If some tables could not be processed you are told how many, and retrying continues from what is left.
Which assets you can pin
| Project | Assets you can pin |
|---|---|
| Account project | Official packs, public assets, and assets you own or co-edit |
| Local project | Official packs and assets stored on this device (account assets are excluded even while signed in) |
An empty list is almost always this scope at work. An account dictionary pointing at a device-local pack, or the reverse, would fail at publish time, so those combinations are filtered out where you pick them.