Node.js Developer Guide
Other documentationsDemoCommunityGitHub
  • Forest Admin
  • Getting started
    • How it works
    • Quick start
    • Install
      • Create your agent
      • Expose an HTTP endpoint
        • For standalone agents
        • On Express
        • On Koa
        • On Fastify
        • On NestJS
      • Autocompletion & Typings
      • Troubleshooting
    • Migrating legacy agents
      • What's new
      • Pre-requisites
      • Recommendations
      • Migration steps
        • Run new agent in parallel
        • Configure database connection
        • Code transformations
          • API Charts
          • Live Queries
          • Smart Charts
          • Route overrides
          • Smart Actions
          • Smart Fields
          • Smart Relationships
          • Smart Segments
        • Compare schemas
        • Swap agents
      • Post-migration
        • Dropping Sequelize
        • Optimize your agent
  • Data Sources
    • Getting Started
      • Collection selection
      • Naming conflicts
      • Cross-data source relationships
      • Query interface and Native Queries
        • Fields and projections
        • Filters
        • Aggregations
    • Provided data sources
      • SQL (without ORM)
      • Sequelize
      • Mongoose
      • MongoDB
    • Write your own
      • Replication strategy
        • Persistent cache
        • Updating the replica
          • Scheduled rebuilds
          • Change polling
          • Push & Webhooks
        • Schema & References
        • Write handlers
      • Translation strategy
        • Structure declaration
        • Capabilities declaration
        • Read implementation
        • Write implementation
        • Intra-data source Relationships
      • Contribute
  • Agent customization
    • Getting Started
    • Actions
      • Scope and context
      • Result builder
      • Static Forms
      • Widgets in Forms
      • Dynamic Forms
      • Form layout customization
      • Related data invalidation
    • Charts
      • Value
      • Objective
      • Percentage
      • Distribution
      • Leaderboard
      • Time-based
    • Fields
      • Add fields
      • Move, rename and remove fields
      • Override binary field mode
      • Override writing behavior
      • Override filtering behavior
      • Override sorting behavior
      • Validation
    • Hooks
      • Collection hook
      • Collection override
    • Pagination
    • Plugins
      • Provided plugins
        • AWS S3
        • Advanced Export
        • Flattener
      • Write your own
    • Relationships
      • To a single record
      • To multiple records
      • Computed foreign keys
      • Under the hood
    • Search
    • Segments
  • Frontend customization
    • Smart Charts
      • Create a table chart
      • Create a bar chart
      • Create a cohort chart
      • Create a density map
    • Smart Views
      • Create a Map view
      • Create a Calendar view
      • Create a Shipping view
      • Create a Gallery view
      • Create a custom tinder-like validation view
      • Create a custom moderation view
  • Deploying to production
    • Environments
      • Deploy on AWS
      • Deploy on Heroku
      • Deploy on GCP
      • Deploy on Ubuntu
      • Deploy on Azure
    • Development workflow
    • Using branches
    • Deploying your changes
    • Forest Admin CLI commands
      • init
      • login
      • branch
      • switch
      • set-origin
      • push
      • environments:create
      • environments:reset
      • deploy
  • Under the hood
    • .forestadmin-schema.json
    • Data Model
      • Typing
      • Relationships
    • Security & Privacy
Powered by GitBook
On this page
  • Installation
  • Usage

Was this helpful?

  1. Agent customization
  2. Plugins
  3. Provided plugins

Flattener

This is the official documentation of the @forestadmin/agent Node.js agent.

Forest Admin user interface is designed with "flat" Collection structure in mind. This paradigm may not be the best fit for your data model if you are using a NoSQL database with nested documents.

In this case, you can use the provided flattener plugin to flatten your data model before sending it to Forest Admin.

Installation

npm install @forestadmin/plugin-flattener

Usage

Three methods are available to flatten your data model: flattenColumn, flattenJsonColumn and flattenRelation.

flattenColumn

This method allows you to flatten deeply nested columns of your models.

Note that when using this method, the collection won't be filterable nor sortable on the target columns.

const { flattenColumn } = require('@forestadmin/plugin-flattener');

agent.customizeCollection('customer', collection => {
  collection.use(flattenColumn, {
    // Name of the column to flatten into the root model
    columnName: 'address',

    // Subfields to flatten (defaults to all subfields up to the `level` setting)
    include: ['street', 'city', 'country:name', 'country:isoCode'],

    // Subfields to exclude from flattening (defaults to none)
    exclude: [],

    // When flattening a subfield, the plugin will flatten all subfields up to the
    // `level` setting.
    // Defaults to 1 and is ignored if `include` is specified.
    level: 1,

    // Either if the created columns should be readonly or not (defaults to false)
    readonly: true,
  });
});

flattenJsonColumn

Please note that this plugin is meant for SQL data sources with primitive JSON columns.

This method allows you to flatten deeply nested primitives JSON columns of your models.

Note that when using this method, the collection won't be filterable nor sortable on the target columns.

const { flattenJsonColumn } = require('@forestadmin/plugin-flattener');

agent.customizeCollection('customer', collection => {
  collection.use(flattenJsonColumn, {
    // Name of the column to flatten into the root model
    columnName: 'address',

    // A json object representing a subset of the shape of the data in
    // the json column, with keys the column names, and values either json (to flatten further)
    // or the primitive type.
    columnType: {
      street: 'String',
      city: 'String',
      country: { name: 'String', isoCode: 'String' },
    },

    // Either if the created columns should be readonly or not (defaults to false)
    readonly: true,

    // Either if original column should be kept or not (defaults to false)
    keepOriginalColumn: true,
  });
});

flattenRelation

It is useful when you want to repatriate multiple fields inside one collection.

const { flattenRelation } = require('@forestadmin/plugin-flattener');

agent.customizeCollection('customer', collection => {
  return collection.use(flattenRelation, {
    relationName: 'address',

    // Subfields to flatten (defaults to all subfields of the relation)
    include: ['street', 'city', 'country:name', 'country:isoCode'],

    // Subfields to exclude from flattening (defaults to an empty array)
    exclude: [],

    // Either if the created columns should be readonly or not (defaults to false)
    readonly: true,
  });
});

Note that nested relations are supported using the : separator.

const { flattenRelation } = require('@forestadmin/plugin-flattener');

agent.customizeCollection('customer', collection => {
  return collection.use(flattenRelation, { relationName: 'address:country' });
});
PreviousAdvanced ExportNextWrite your own

Last updated 1 year ago

Was this helpful?

This method allows you to import fields from a given or relations.

one-to-one
many-to-one