5.94 dependent lookup not invalidated if parent changes but same label exists

Please report bugs and any annoyances here. Kindly include all possible details: steps to reproduce, expected result, actual result, screenshots, ... etc.
Post Reply
User avatar
onoehring
AppGini Super Hero
AppGini Super Hero
Posts: 986
Joined: 2019-05-21 22:42
Location: Germany
Contact:

5.94 dependent lookup not invalidated if parent changes but same label exists

Post by onoehring » 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:

Code: Select all

table containing data for lookup A:

ID | label
------------
1  | x
2  | a
4  | b
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

Code: Select all

table containing data for lookup B:

ID | FK  | label
-------------------
5  | 2   | x
6  | 4   | x
7  | 2   | someA
8  | 4   | someB  
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

User avatar
onoehring
AppGini Super Hero
AppGini Super Hero
Posts: 986
Joined: 2019-05-21 22:42
Location: Germany
Contact:

Re: 5.94 dependent lookup not invalidated if parent changes but same label exists

Post by onoehring » 2021-03-07 08:23

Hi,

it seems to go even one step further:
Lookup A, Lookup B (dependent on A), lookup C (dependent on B).

If lookup A changes, not lookup B (nor lookup C) get invalidated [edit]sometimes[/edit] and emptied to force the user to choose matching values.

Olaf


Post Reply