Responsible group injection visibility issue

[Neu-Maximilian]

Dear GLPI plugin user.

⚠️ Please never use standard issues to report security problems. See security policy for more details. ⚠️

BEFORE SUBMITTING YOUR ISSUE, please make sure to read and follow these steps:

• We do not track feature requests nor enhancements here. Propose them on the suggest dedicated site.
• Keep this tracker in ENGLISH. If you want support in your language, the community forum is the best place.
• Always try to reproduce your issue at least on latest stable release.

The GLPI team.

Professional Support

We do not guarantee any processing / resolution time for community issues.

If you need a quick fix or any guarantee, you should consider to buy a GLPI Network Subscription.

More information here: https://glpi-project.org/subscriptions/

Code of Conduct

By submitting this issue, you agree to follow hereinabove rules and Contribution guide

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

Please search to see if an issue already exists for the bug you encountered.

• I have searched the existing issues

GLPI Version

What version of our GLPI are you running?

11.0.4

Plugin version

What version of datainjection are you running?

2.15.3

Bug description

The responsible group is not visually shown in GLPI after import, even though the database seems to contain the expected value.

Relevant log output

None.

Page URL

The URL of an equipment with a responsible group injected.

Steps To reproduce

Steps to reproduce the behavior.

1. Create or use a DataInjection model for an equipment type supporting responsible group import.
2. Map the responsible group field.
3. Import a CSV row with a valid responsible group value.
4. Open the imported item in GLPI.

Your GLPI setup information

Please copy and paste information you will find in GLPI in Setup > General menu, System tab.

Anything else?

Root cause :

The plugin was sending scalar group fields in some cases instead of normalizing them into the GLPI relation payload keys expected for equipment group assignment. This made the persistence path inconsistent with the UI-visible assignment path.

Proposed fix :

Normalize groups_id, groups_id_normal, and groups_id_tech into _groups_id / _groups_id_tech in the shared injection flow, even when the search option metadata does not contain the expected nested joinparams structure.