Hi,
I am having trouble setting this up. I wish to configure a DB so that I can get a single form as in the attachment.
I also wish to add a quick search field at the top of the page rather than an advanced filter form. This is a simple product catalog for spare parts.
Which field should be the lookup field to the other table?
Thanks
Frengix
Problem with catalog DB Relation
Problem with catalog DB Relation
- Attachments
-
- db.png (10.18 KiB) Viewed 3093 times
Re: Problem with catalog DB Relation
You'd need 3 tables: roots, items and parts.
Parts table would have a lookup field to roots and another lookup to items, as well as normal fields for manufacturing#, part# and image. The parts table would in this way look similar to your layout above.
You can use the quick search box above the parts table to perform, well .., quick searches instead of using the advanced filters page
Parts table would have a lookup field to roots and another lookup to items, as well as normal fields for manufacturing#, part# and image. The parts table would in this way look similar to your layout above.
You can use the quick search box above the parts table to perform, well .., quick searches instead of using the advanced filters page


- 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
- Check our other plugins and get a generous discount of up to 30% when buying 2 or more plugins.
- Need personalized consulting on your specific app and customizations? Book an online call with me here.
Re: Problem with catalog DB Relation
Hi,
Thanks for your reply.
That solved my problem.
Is there a way to not show all results when the page loads. I need to only show results when the user search for it.
Thanks
Thanks for your reply.
That solved my problem.

Is there a way to not show all results when the page loads. I need to only show results when the user search for it.
Thanks