Fix Custom Dropdown filtering in table questions - #42
Closed
UncleTomsCabi wants to merge 1 commit into
Closed
UncleTomsCabi wants to merge 1 commit into
UncleTomsCabi wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using GLPI Custom Dropdowns inside table questions, all dropdown definitions display the same combined list of values.
This happens because all custom dropdowns use the same database table (
glpi_dropdowns_dropdowns), but the current implementation does not apply the system criteria that distinguish each dropdown definition.Solution
This change updates the table question implementation to correctly filter Custom Dropdown values by applying the item's
getSystemSQLCriteria()when:As a result, each Custom Dropdown now displays only the values that belong to its own definition.
Before
After