Openbravo Issue Tracking System - POS2
View Issue Details
0055149POS2Corepublic2024-04-10 08:162025-03-27 12:13
marvintm 
Triage Platform Base 
normalminorhave not tried
closedduplicate 
5
 
 
No
No
0055149: Automatically generated configuration names are not specific enough
The BaseFormInput component is automatically using a configuration if present, so that it is possible to inject additional buttons to it:

https://gitlab.com/openbravo/product/pmods/org.openbravo.core2/-/blob/master/web-jspack/org.openbravo.core2/src/components/BaseFormInput/BaseFormInput.jsx?ref_type=heads#L114 [^]

This is great because it allows for modules to add buttons to such inputs. However, the names of the expected configuration in practice, when these inputs are coming from a filter in a FilterableGrid, are just

"fieldName_additionalButtons"

This seems to be not specific enough, and we believe the probability that we will have collisions later on will be high.
Create a FilterableGrid with some filter.
Check the name of the expected configuration for the input of the filters.
The simplest solution seems to be to concatenate the ids of the "parent" components on the name, so that different FilterableGrids have different configurations for their filters.
No tags attached.
Issue History
2024-04-10 08:16marvintmNew Issue
2024-04-10 08:16marvintmAssigned To => Triage Platform Base
2024-04-10 08:16marvintmOBNetwork customer => No
2024-04-10 08:16marvintmTriggers an Emergency Pack => No
2024-04-10 08:54AugustoMauchStatusnew => acknowledged
2024-05-06 10:33alostaleSeveritymajor => minor
2024-06-17 08:38AugustoMauchStatusacknowledged => scheduled
2025-03-27 12:13hgbotNote Added: 0177523
2025-03-27 12:13hgbotStatusscheduled => closed
2025-03-27 12:13hgbotResolutionopen => duplicate

Notes
(0177523)
hgbot   
2025-03-27 12:13   
Issue exported to Jira: https://openbravo.atlassian.net/browse/RM-24256 [^]