Locations
Associa branch locations (the C3 ACCESS_LOCATION analogue) that manage associations and roll up to a region. Each association is managed by one location.
Migration Requirements
Required for Import
Yes - Required
Retention History
Include every branch location that manages an active association.
Usage Notes
•Each association is managed by one branch location (the C3 ACCESS_LOCATION analogue).
•References its parent region via Region ID; load regions first.
•Resolves the C3 ASSOCIATION.location_id link for each association.
Fields (9)
Expand a field to see example values and, where necessary, additional business context
| Field | Type | Description | Attributes | |
|---|---|---|---|---|
| Location Main | ||||
Location ID | Text | Unique identifier for the source-system branch location | Required | |
Location ID Unique identifier for the source-system branch location Examples LOC-001 12345 PHX-01 Business Context Identifies a unique branch location from your source system so associations can reference it. Provide any stable unique identifier—numeric IDs or codes both work. | ||||
Region ID | Text | Source-system identifier of the region this location rolls up to | Optional | |
Name | Text | The name of the branch location | Required | |
Code | Text | Short location code used for reference and C3 round-tripping | Optional | |
| Location Address | ||||
Address | Text | Full address of the branch location including street, suite/unit, city, state, and zip code | Optional | |
| Contact Information | ||||
Phone | Text | Phone number for the branch location | Optional | |
Email | Text | Email address for the branch location | Optional | |
| Notes | ||||
Note | Text | Free-text note about the branch location | Optional | |
| Additional Data | ||||
Additional Data | JSON Object | Any extra information from your source system | Optional | |
Relations
regionRegionsmany-to-oneThe region this location rolls up to
associationsAssociationsone-to-manyAssociations managed by this branch location