In many areas of the application a field gets it lists of possible values via a table relationship. When this relationship is conditional on the value of another field the way tables are filtered breaks down.

For example in payment reconciliation application an account no. field may contain different sets of data depending on the field account type.

At the moment the application handles this scenario terribly. It basically appears to use the first of the possible relationships - which for example in payment reconciliation is useless as it usually a customer or vendor - not a general ledger account.

The way to fix this (given that you can have different relationships per row) appears to be to surface those possible conditional relationships in the interface and allow setting that constraint first and remembering as a default in the future until changed.

This would help in many areas of the application, especially given how valuable and helpful those conditional relationships are.