Bug is SPM when using lookup fields

Please report bugs and any annoyances here. Kindly include all possible details: steps to reproduce, expected result, actual result, screenshots, ... etc.
Post Reply
wilmira
Veteran Member
Posts: 67
Joined: 2013-07-11 18:00

Bug is SPM when using lookup fields

Post by wilmira » 2018-09-04 18:16

Hello Ahmad,

Just to inform you that I have noticed that, when using lookup fields in the filter generated by SPM, the lookup field is not working properly.

What happens is that when you have the parent field and the child field in the filter, the child field will list all the possible items for the parent field, lets say you have as parent field 2 options(Optino 1 and Option 2), and you have 2 children options for each parent option (Option11, Option12, Option21 and Option22). All the options will be shown in the filter page, no matter if you choose to filter Option1 or Option2.
Attachments
SPMbug1.png
SPMbug1.png (41.24 KiB) Viewed 1661 times

User avatar
a.gneady
Site Admin
Posts: 1281
Joined: 2012-09-27 14:46
Contact:

Re: Bug is SPM when using lookup fields

Post by a.gneady » 2018-09-13 15:26

I'm so sorry for the long delay and thanks for reporting this issue. We're aware of it and plan to implement cascading lookups in future releases of SPM. Stay tuned!
:idea: AppGini plugins to add more power to your apps:
  • DataTalk is an innovative AppGini plugin based on ChatGPT that allows you to interact with your AppGini database using natural language questions, without writing any SQL. Check the demo video
  • Mass Update plugin: Update multiple records at once and improve your workflow efficiency.
  • Check our other plugins and get a generous discount of up to 30% when buying 2 or more plugins.

Post Reply