PHPackages                             oplatform-club/platform-serialised-fields - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. oplatform-club/platform-serialised-fields

ActiveLibrary

oplatform-club/platform-serialised-fields
=========================================

Oro Platform Serialized Fields

2.5.1(8y ago)02OSL-3.0PHPPHP >=7.0

Since Dec 22Pushed 8y ago1 watchersCompare

[ Source](https://github.com/oplatform-club/OroEntitySerializedFieldsBundle)[ Packagist](https://packagist.org/packages/oplatform-club/platform-serialised-fields)[ Docs](https://github.com/oroinc/OroEntitySerializedFieldsBundle)[ RSS](/packages/oplatform-club-platform-serialised-fields/feed)WikiDiscussions master Synced today

READMEChangelog (1)Dependencies (1)Versions (45)Used By (0)

OroEntitySerializedFieldsBundle
===============================

[](#oroentityserializedfieldsbundle)

This document contains a little introduction into "Oro Entity Serialized Fields" package, information on how to download and install.

Table of content
----------------

[](#table-of-content)

- [Fundamentals](#fundamentals)
- [Requirements](#requirements)
- [Installation](#installation)
- [Run unit tests](#run-unit-tests)

Fundamentals
------------

[](#fundamentals)

ORO Platform provides ability to have custom entities or extend entities with new custom fields.

The package allows to avoid schema update when you create custom field. Although this field come with some restrictions.

Such fields data stores in `serialized_data` column as serialized array. Field `serialized_data` is hidden from UI in entity config page.

Not supported features:

- grid filtering and sorting
- segments and reports
- charts
- search
- relations, enums and option set field types
- data audit
- usage of such fields in Doctrine query builder

After installation (described below) a new field called **Storage Type** appears within **New field** creation page where you will be offered to choose between two storage types:

- `Table Column` option will allow to create custom field as usual;
- `Serialized field` option means that you can avoid schema update and start to use this field imediately, but should take into account, that field types are limited in this case to:
    - string
    - integer
    - smallint
    - bigint
    - boolean
    - decimal
    - date
    - datetime
    - text
    - float
    - money
    - percent

To create a serialized field via migration the [SerializedFieldsExtension](./Migration/Extension/SerializedFieldsExtension.php) can be used. Here is an example:

```