feat(migration): add type renaming to resolve native asset name conflicts

[Rom1-B]

• Replace : feat(migration): add type renaming to resolve native asset name conflicts #472

---

• I have performed a self-review of my code.
• I have added tests (when available) that prove my fix is effective or that my feature works.
• This change requires a documentation update.

Description

• It fixes !42658
• It is not possible to migrate an asset from the genericobject plugin if its name is similar to an asset in the GLPI core. This fix allows users to rename an asset so they can continue the migration.

Screenshots (if appropriate):

Conflict:

Migrate

[stonebuzz]

Something doesn't seem to be working correctly in the renaming process.

Let's take the KCM object as an example:

I want to rename it to KVM.

After saving the change, GLPI displays a success message indicating that the operation completed successfully:

However, after refreshing the page, I can see that the object has not actually been renamed and is still displayed as KCM.

I then retry the exact same operation, and this time it succeeds:

The object is now correctly renamed to KVM:

It looks like the first attempt returns a success message even though the rename is not actually applied. The change only takes effect after performing the exact same operation a second time.

[stonebuzz]

If a plugin (in this case, Fields) references these objects, it breaks the migration process.

Traitement du plugin « fields »...
Installation des tables MySQL

In DBmysql.php line 417:
                                                                                                                                                                 
  MySQL query error: Table 'sopra.glpi_plugin_genericobject_kcms' doesn't exist (1146) in SQL query "SHOW COLUMNS FROM `glpi_plugin_genericobject_kcms`". 

[stonebuzz]

Hello,

It appears that the foreign keys associated with the renamed GenericObject objects were not renamed accordingly.

This seems to match the issue described in the following support ticket:
https://support.teclib.com/front/ticket.form.php?id=42658

[stonebuzz]

waiting customer feedback