5.94 dependent lookup not invalidated if parent changes but same label exists
Posted: 2021-03-07 08:15
Hi,
The setting
lookup A and lookupB, where lookup B is dependent on lookup A (filters value depending of the selected value in lookup A)
For lookup A the following exit in table A:
Lookup B is dependent on lookup A (and should change, when lookup A is changed. The source table for lookup B contains these, where FK is the primary key of table A
The problem
Now, when lookup A contains Value a (PK 2), lookup B offers x (PK 5) and someA (PK 7). Ok. Let's assume you save the record with these settings.
Go back to editing the record and change lookup A to b (PK 4). No change will happen in lookup B (if I did not make an error testing): Lookup b will still be showing x - which is the wrong x now, as it should be the x with the different PK
The problem is, that the user will not see, that he needs to change/adjust lookup B is there is still some value left in the lookup B after lookup A has been changed.
Can anyone reproduce this?
Olaf
The setting
lookup A and lookupB, where lookup B is dependent on lookup A (filters value depending of the selected value in lookup A)
For lookup A the following exit in table A:
Code: Select all
table containing data for lookup A:
ID | label
------------
1 | x
2 | a
4 | b
Code: Select all
table containing data for lookup B:
ID | FK | label
-------------------
5 | 2 | x
6 | 4 | x
7 | 2 | someA
8 | 4 | someB
Now, when lookup A contains Value a (PK 2), lookup B offers x (PK 5) and someA (PK 7). Ok. Let's assume you save the record with these settings.
Go back to editing the record and change lookup A to b (PK 4). No change will happen in lookup B (if I did not make an error testing): Lookup b will still be showing x - which is the wrong x now, as it should be the x with the different PK
The problem is, that the user will not see, that he needs to change/adjust lookup B is there is still some value left in the lookup B after lookup A has been changed.
Can anyone reproduce this?
Olaf