fw_branches
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| fw_branches [2025/03/11 11:44] – gloria | fw_branches [2025/03/11 11:49] (current) – gloria | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * **Branding support** through logos & invitation headers. | * **Branding support** through logos & invitation headers. | ||
| - | This table enables seamless handling of multiple branches under a single client while maintaining structured relationships. | ||
| - | ---- | ||
| ==== Table Structure ==== | ==== Table Structure ==== | ||
| Line 24: | Line 22: | ||
| - | ==== Relationships ==== | ||
| - | * **clientid** → References **fw_clients** table (Each branch belongs to one client). | ||
| - | * **branchcode** → Must be **unique** across all branches. | ||
| - | ---- | ||
| - | ==== Example Data ==== | ||
| - | ^ **id** ^ **clientid** ^ **branchname** | ||
| - | | 5 | 1 | Swietelsky | ||
| - | | 3 | 1 | Zevenaar-Didam | ||
| - | | 4 | 1 | Groningen Spoorzone | ||
| - | | 6 | 1 | EdesPoort | ||
| - | | 7 | 1 | Leeuwarden | ||
| - | | 8 | 1 | Maaslijn | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Common Issues & Solutions ==== | ||
| - | |||
| - | **Issue:** " | ||
| - | **Solution: | ||
| - | |||
| - | **Issue:** " | ||
| - | **Solution: | ||
| - | |||
| - | **Issue:** "Null values for website or location." | ||
| - | **Solution: | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Notes ==== | ||
| - | - Each **client** can have **multiple branches**, each requiring a **unique branchcode**. | ||
| - | - Logos and invitation headers should follow the **recommended dimensions**. | ||
| - | |||
| - | ---- | ||
fw_branches.1741693493.txt.gz · Last modified: 2025/03/11 11:44 by gloria
