Academy / Multi-Location Architecture / Office Data and Weave UI — Multi-Source Configurations

Office Data and Weave UI — Multi-Source Configurations

Lesson 3.3 ⏱ ~5 min

💡 Why This Matters

Multi-source organizations are the most complex accounts you'll encounter. Understanding how multiple SyncApps feed into a flexible UI configuration is essential for debugging and for planning integrations with large enterprise customers.

🎯 What You'll Learn

  • How multiple data sources feed multiple SyncApps and ultimately multiple Weave UIs
  • The case of all data from all sources combined into a single Weave UI
  • Complex mapping: 3 sources with 9 total locations mapped to 3 UIs with different location groupings
  • Why location data is the most granular unit and why UI grouping is entirely configurable
  • The conceptual mental model: think of SourceTenantId as the atomic unit of data

Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

When an organization has multiple data sources (e.g., 3 databases each with data for 3 locations), three SyncApps run. The resulting 9 location-tagged data sets can be configured into any number of UIs. The office might want: one giant UI showing all 9 locations, or 9 separate UIs, or 3 UIs grouping each source's locations together, or any arbitrary combination. The SourceTenantId is the atomic unit — it represents data for one location from one source. The Weave UI simply selects which SourceTenantIds to display.

🏷 Key Concepts

Multi-Source Configuration Multiple SyncApps SourceTenantId as Atomic Unit Arbitrary UI Grouping Enterprise Account Configuration

Key Takeaways

01Multiple SyncApps produce multiple sets of location-tagged data — how those are surfaced in UI is entirely configurable
02The number of Weave UIs doesn't have to match the number of data sources or the number of locations
03Each 'customer office' in the architecture diagrams corresponds to one SourceTenantId
04When debugging multi-location issues, always start by identifying which SourceTenantId the data belongs to