This project is not covered by Drupal’s security advisory policy.

Not stable.

Record entity:

This module provides a "Record" entity type, which is ready to use. It is useful for random datasets that a business needs, which you want to separate from content (separate both the actual content, editor UIs, and the field config).

Record properties field:

It also has a field which is configurable with regards to the columns. This is perfect for flat datasets with many columns (think of data on a large spreadsheet). You could support 100s of columns with one field: only two database tables, the main table and the revision table.

It's just a field, so you can also use it alongside your regular fields for the functionality you need. So far it works very nicely with ongoing migrations, where data is managed elsewhere.

The field module should only be considered by advanced developers at this point, and is best suited to content that is regularly updated through migrations.

Readiness:

The Record entity is usable, as it's a vanilla entity. But if you are a developer (not just a site builder at this stage) interested in the Record properties field for your project, then you should contact me in community Slack or via my contact form, so I can talk through the details. This module is early days.

Roadmap:

  • Some improved UX in Views and Field config.
  • Auto-create property fields during migrations.
  • No data loss adding removing properties (dataset size may limit this).
  • Tools to help move data from properties to real fields.
  • Possible refactoring and tests
Supporting organizations: 

Project information

Releases