# Datatables, Fields & Data

## Flows

Flows are now part of your Buzzy app definition and should be defined alongside your datamodel.

Flows describe functional behavior such as navigation paths, branching logic, and lifecycle stages. This context helps Buzzy generate screens and blueprint structure that better match your intended app behavior.

For flow-first requirement design, see:

* [Flows](/the-building-blocks/flows.md)
* [Functional Design: Flows](https://docs.buzzy.buzz/the-building-blocks/pages/nXKIBokPljM9E7i9shdv#id-1.-flows)

## Datatables - Working with Data in Buzzy

Working with data in Buzzy is done through **Datatables**: an intuitive and powerful solution that makes designing great apps straightforward. Datatables are used to store data, build forms, collect data, and add interactivity with sophisticated relationship modeling.

Datatables are one core part of your app definition. You can now also define **Flows** as part of the same app context, so functionality described in flow diagrams works in combination with your brief, datamodel, blueprint, and theme.

This helps you define requirements more completely: flows make user journeys and process states explicit, while datatables define the data structure needed to support them. In practice, this usually leads to better generated fields, relationships, and screen behavior.

**New to Buzzy's datamodel?** Start with our [Buzzy Datamodel Overview](/the-building-blocks/datatables-fields-and-data/buzzy-datamodel-overview.md) for a comprehensive guide to understanding relationships, fields, and how to work with data programmatically.

Please note - Datatables were previously called "Microapps" - some code snippets may still refer to a microapp (e.g. the API end-point `microappdata`). If in doubt, email support.

{% hint style="info" %}
**Note** This section documentation may include references to deprecated field types
{% endhint %}

### Table of contents

* [Buzzy Datamodel Overview](/the-building-blocks/datatables-fields-and-data/buzzy-datamodel-overview.md) - **Start here for a comprehensive guide**
* [Introduction to Fields](/the-building-blocks/datatables-fields-and-data/introduction-to-fields.md)
* [Basic Fields](/the-building-blocks/datatables-fields-and-data/basic-fields.md)
* [Advanced Fields](/the-building-blocks/datatables-fields-and-data/advanced-fields.md)
* [Display Fields](/the-building-blocks/datatables-fields-and-data/display-fields.md)
* [Metadata Fields](/the-building-blocks/datatables-fields-and-data/metadata-fields.md)
* [Filter Controls](/the-building-blocks/datatables-fields-and-data/filter-controls.md)
* [External Fields](/the-building-blocks/datatables-fields-and-data/external-fields.md)
* [Sort Fields](/the-building-blocks/datatables-fields-and-data/sort-fields.md)
* [Formula language](/the-building-blocks/datatables-fields-and-data/formulas.md)
* [Datatable to Datatable Relationship](/the-building-blocks/datatables-fields-and-data/datatable-to-datatable-relationships.md)
* [Security and Access Control](/the-building-blocks/datatables-fields-and-data/security-and-access-control.md)
* [Displaying a field based on the values of other fields](/the-building-blocks/datatables-fields-and-data/displaying-a-field-based-on-the-values-of-other-fields.md)
* [Hiding a field based on role using a display formula](/the-building-blocks/datatables-fields-and-data/hiding-a-field-based-on-role-using-a-display-formula.md)
* [Importing data from a text file](/the-building-blocks/datatables-fields-and-data/importing-data-from-a-text-file.md)
* [Importing data from a URL](/the-building-blocks/datatables-fields-and-data/importing-data-from-a-url.md)
* [Import data from Datatable](/the-building-blocks/datatables-fields-and-data/import-data-from-datatable.md)
* [Export data using Chrome](/the-building-blocks/datatables-fields-and-data/export-data-using-chrome.md)
* [Export data in Browser](/the-building-blocks/datatables-fields-and-data/export-data-in-browser.md)
* [Export data using Safari](/the-building-blocks/datatables-fields-and-data/export-data-using-safari.md)
* [Datatable Field Types - Cheat Sheet](/the-building-blocks/datatables-fields-and-data/datatable-field-type-cheat-sheet.md)

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.buzzy.buzz/the-building-blocks/datatables-fields-and-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.