Problem with catalog DB Relation

If you're a new user of AppGini, feel free to ask general usage questions, or look for answers here.
Post Reply
frengix
Posts: 6
Joined: 2015-05-12 17:53

Problem with catalog DB Relation

Post by frengix » 2015-05-12 18:00

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
Attachments
db.png
db.png (10.18 KiB) Viewed 3087 times

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

Re: Problem with catalog DB Relation

Post by a.gneady » 2015-05-12 20:35

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 :D
:idea: AppGini plugins to add more power to your apps:

frengix
Posts: 6
Joined: 2015-05-12 17:53

Re: Problem with catalog DB Relation

Post by frengix » 2015-05-13 13:43

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

Post Reply