API Requests to Fields plugin

[0r1k]

Hello.
GLPI version 11.0.2
Plugin version 1.23.0
Requests to legacy api api.php/v1 are not working.
What request should I use to get data from an additional field?

[jeanmachadocx]

GLPI 11.0.2
Plugin version 1.23.0

I am experiencing an issue when trying to populate custom fields from the Plugin Fields extension via the API in GLPI 11.0.2 using Plugin Fields 1.23.0. Even when sending the payload in the format expected for version 11, the values are simply not applied to the ticket.

The JSON being sent looks like this:

_plugin_fields: { "3": { "9": "teste" } }

Where 3 is the container ID and 9 is the field ID. However, after creating the ticket, the field remains empty in GLPI. This behavior is consistent and can be observed in the attached screenshot.

In GLPI 10, this process worked correctly by sending the field names directly in the JSON, for example:

socidfield: "value", datadeocorrnciafield: "value", mittretticafield: "value", mittretcnicafield: "value"

In other words, in the previous version, custom fields were filled without any issues. In GLPI 11, the old format stopped working, and the new _plugin_fields format also does not seem to have any effect.

The expected behavior is that the value sent for the custom field should be stored in the ticket. The current behavior is that the ticket is created but the custom field remains empty, suggesting a possible bug in the Plugin Fields plugin or in how GLPI 11 handles these fields through the API.

[stonebuzz]

Hi @0r1ks

I am not encountering any issues with the Legacy API v1.

Here is an example of a request that allows me to retrieve information from a container:

** Session Initialization**

curl -X GET \
-H 'Content-Type: application/json' \
-H "Authorization: Basic Z2xwaTpnbHBp" \
-H "App-Token: R9Banz0KMSc9ghsed5cnNeGbPqHHqU2YNZ4Vu1gu" \
'http://glpi11bf.localhost/apirest.php/initSession'

** Retrieve Container Data**

You can request data from the container PluginFieldsTicketticketinfo with ID 8.
It is also possible to filter by itemtype and items_id using the endpoint apirest.php/search/:itemtype/.

curl -X GET \
-H 'Content-Type: application/json' \
-H "Session-Token: h2scnfov6bqjo17752nhuqgv73" \
-H "App-Token: R9Banz0KMSc9ghsed5cnNeGbPqHHqU2YNZ4Vu1gu" \
'http://glpi11bf.localhost/apirest.php/PluginFieldsTicketticketinfo/8'

** Example API Response**

{
  "id": 8,
  "items_id": 60,
  "itemtype": "Ticket",
  "plugin_fields_containers_id": 2,
  "entities_id": 0,
  "customfield": "my custom value",
  "links": [
    {"rel": "Ticket", "href": "http://glpi11bf.localhost/api.php/v1/Ticket/60"},
    {"rel": "PluginFieldsContainer", "href": "http://glpi11bf.localhost/api.php/v1/PluginFieldsContainer/2"},
    {"rel": "Entity", "href": "http://glpi11bf.localhost/api.php/v1/Entity/0"}
  ]
}

Best regards

[stonebuzz]

@jeanmachadocx

Please open a new issue, as your problem is not the same as the one discussed here.

[github-actions]

This issue has been closed as we only track bugs here.

You can get community support on forums or you can consider taking a subscription to get professional support.
You can also contact GLPI editor team directly.