Linking tables - sort of

[shasta59]

Using 5.31

Okay, I am stumped and maybe am not looking at it the right way. (Everyone I am sure has hit this wall - you think and think and think and cannot figure out the simple solution to a problem until someone else triggers something that gives the answer).

Here is what I need to do:

I have a service repair order. This is simple. Name, unit, and all other details are easy. However what I need to do is set it up so that the person working on the unit can add in 1 part or 10 parts on different lines. (or it may be 50 parts needed). I do not want to create X number of fields but need to allow the end user to put in the part number, part description, quantity and inventory site and then if needed enter the next part etc. I know this has to be done with two different tables. When they finish adding a part there could be a button which says Add Another Part?

I need it to appear seamless. The user creates the repair order and then further down enters the parts used or needed. Then when they bring up the repair order again it shows the details and all the parts used or ordered. So I need to figure out how to, on one screen show the order details and the parts which are associated with that order. It is very important the service repair order and the parts for that order are linked.

The client needs to be able to just look at parts which are outstanding and which parts are outstanding for that repair order.

It should not be tough but I cannot figure out how to get appgini to do this (if It can)?
Think of membership_users and membership_userrecords.

Suggestions? (If the above explanation does not make sense let me know and I will rewrite it)

Alan

[a.gneady]

Hi Alan,

My guess from your description is that it can be done on a custom page that still uses code provided by AppGini for most of the functionality. If you post some sketch or mockup of what you need to do, it would be very helpful to figure out where to start.

[tuxor]

First, I think yo need to create a Parent/child relationship for this:
"I have a service repair order. This is simple. Name, unit, and all other details are easy. However what I need to do is set it up so that the person working on the unit can add in 1 part or 10 parts on different lines. (or it may be 50 parts needed). I do not want to create X number of fields but need to allow the end user to put in the part number, part description, quantity and inventory site and then if needed enter the next part etc. I know this has to be done with two different tables. When they finish adding a part there could be a button which says Add Another Part?"

Then, you can create a report with parent/child relationship and with the specification to view some fields for X user.

All we can do with appgini, just need to know how to do that. Maybe you should to do the analysis again, thinking about the parent/children relationship.