Plugin Fields vs Native Fields in GLPI 11

Comparison between the Fields plugin and the native options in GLPI 11 for custom fields: when to use each one, limitations and migration.

Custom fields are essential to adapt GLPI to your organization's reality. See when to use the Fields plugin and when the native features of GLPI 11 are sufficient.

Plugin Fields

Fields allows you to add custom fields to any type of item in GLPI: tickets, computers, users, contracts, etc. Features:

  • Types: text, dropdown, checkbox, date, number, URL, yes/no
  • Grouping in containers (tabs)
  • Visibility by profile
  • Search and reports on custom fields
  • Compatible with GLPI 10 and 11

Custom objects (native GLPI 11)

GLPI 11 allows creating new object types with their own fields, without a plugin. This replaces GenericObject:

  • Create type "Vehicle", "Meeting Room", "Lab Equipment"
  • Custom fields for the new type
  • Integration with inventory, tickets and reports

When to use Fields

  • Adding fields to existing types (ticket, computer, user)
  • Organization-specific information (department, cost center, project)
  • Mandatory fields per ticket category

When to use native objects

  • Creating completely new item types
  • Items that don't fit any existing type
  • Replacing GenericObject when migrating to GLPI 11

Frequently Asked Questions

Yes. Fields has a version compatible with GLPI 11, unlike FormCreator. It remains useful for adding fields to existing item types.

GLPI 11 incorporated custom objects into the core, but custom fields on existing types (such as tickets and computers) still depend on the Fields plugin.

Fields adds fields to existing types (e.g. a 'Department' field on the ticket). Custom objects create new item types (e.g. a 'Vehicle' type with its own fields).

Need help?