Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REST API Field ID changes on Upgrade from 9.5 to 10.0 #714

Closed
chri-bra opened this issue Sep 21, 2023 · 1 comment
Closed

REST API Field ID changes on Upgrade from 9.5 to 10.0 #714

chri-bra opened this issue Sep 21, 2023 · 1 comment

Comments

@chri-bra
Copy link

chri-bra commented Sep 21, 2023

Hi there

We are using Fields (v 1.13.0) on GLPI 9.5.12. (OS Ubuntu 20.04)
One of our custom fields (e.g. "patching status") has the ID 76668. See screenshot.

GLPI 9 5

We are on the migration from GLPI 9.5 to 10.0.
On a new Server (Ubuntu 22.04) and GLPI 10.0.9 and Fileds 1.20.5, the ID of the custom field "patching status" changes. It changes to 76675. Although we have copied/migrated the database. And therefore, in our opinion, the fields or REST API IDs should not change.

GLPI 10

Why does the field ID change? Is it possible to configure somewhere that the numbers/IDs of the REST API stay the same?

@cedric-anne
Copy link
Contributor

Hi,

Previously, in fields plugin, search options IDs were not constant across profiles, and were changing when fields were removed. This was changed in #593 , but we were not able to prevent side effects. With this change, search options IDs will always keep the same ID, whatever the profile used, and whatever the changes made on other fields.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants