Data Management - Tabular
PlaidCloud’s data layer is built around tables (structured row-and-column data) and views (saved queries over tables). Both live inside a project and are powered by the Lakehouse engine, which scales from small reference tables to billion-row analytical datasets without configuration changes.
What’s in This Section
Section titled “What’s in This Section”- Tables and views — what each is, when to use which, and how they interact
- Table explorer — browse and inspect tables in your project
- Publishing data — make project tables available to dashboards, BI tools, and downstream systems
- Selecting the latest record in a large history table — a common pattern with a performance-aware solution
Where Data Comes From
Section titled “Where Data Comes From”Tables are typically populated by workflows — automated pipelines that import data, transform it, and write results back. See Workflows for how to build them, and Workflow step reference for every step type you can use.
For connecting external systems as data sources, see Connections (guide) and Connectors (reference).
Related
Section titled “Related”- Concepts — how tables relate to workflows, dimensions, and the broader data model
- Projects — projects own the tables; tables don’t exist outside a project
- Dashboards — consume published tables for visualization