... | @@ -12,15 +12,14 @@ When creating a field that provides several list of known options (i.e. status, |
... | @@ -12,15 +12,14 @@ When creating a field that provides several list of known options (i.e. status, |
|
**Pros:** Native & dynamic, list of values can be updated at any time by any privileged user, without having to be a developer.\
|
|
**Pros:** Native & dynamic, list of values can be updated at any time by any privileged user, without having to be a developer.\
|
|
Reusable on other fields & entities.\
|
|
Reusable on other fields & entities.\
|
|
Highly extensible.
|
|
Highly extensible.
|
|
|
|
|
|
**Cons:** Requires object storage / data model extension by creating a new entity type for every select list. \
|
|
**Cons:** Requires object storage / data model extension by creating a new entity type for every select list. \
|
|
Object storage has the pointer to the relation, but not the data itself. Views and data access a bit more complex (require define relations).
|
|
Object storage has the pointer to the relation, but not the data itself. Views and data access a bit more complex (require define relations).
|
|
3. **Dynamic select list.**\
|
|
3. **Dynamic select list.**\
|
|
**Pros**: Dynamic, list of values can be updated at any time by any privileged user, without having to be a developer.
|
|
**Pros**: Dynamic, list of values can be updated at any time by any privileged user, without having to be a developer.
|
|
|
|
|
|
Reusable on other fields & entities.\
|
|
Reusable on other fields & entities.\
|
|
Object storage contains the data without having to add relations.\
|
|
Object storage contains the data without having to add relations.\
|
|
**Cons**: Requires some custom development (not drupal native).
|
|
**Cons**: Requires some (minimal) custom development (not drupal native).
|
|
|
|
|
|
|
|
|
|
## Implementing a Dynamic Select List (type 3)
|
|
## Implementing a Dynamic Select List (type 3)
|
|
|
|
|
... | | ... | |