Equipment Repair System

Hi everyone,
I’m creating my first web app that will function as a repair tracking system and have come unstuck, I think I’ve backed myself into a bit of a corner and could use some advice.
The user logs-in and clicks a button to create a new repair. When the ‘new’ button is pressed, a popup appears with input fields for the serial number of the equipment etc. At this stage, nothing is saved in the database until the ‘save’ button at the bottom is pressed which creates a new thing.
My problem is that I would also like a RG or the appearance of a RG where the user can enter the repair work needed. So for example there would be one serial number for the item but it may need multiple work items doing to it. So what I’d like to do is have a blank input field in the work required section that when completed, a new blank field appears below. When the second is filled out, a third blank line appears etc. Happy to press a + button to create the new line if need be.
I’ve found a couple of articles on the forum that use hidden groups as well as collapsing groups and also one that used a listofnumbers to define how many rows are shown. But the issue I’ve got is that these all seem to rely on the filled out rows existing in a thing that can then be counted to know how many rows to show. The corner I’ve backed myself into is that until the ‘save’ button is pressed, the entire repair doesn’t exist as a thing.

My table layout is:
*Item Repair
Make
Model
Serial Number

*Work Required
Repair ID (Type = Item Repair)
Work Required (Type = List of Repair Codes)
Completed By

*Repair Codes
Repair Code
Description
Price

Thanks for any help anyone can give.

1 Like

It seems like you’re facing a common challenge in web app development. One approach you could consider is using client-side JavaScript to dynamically add new input fields for work required as the user fills them out, without necessarily saving the entire repair until the ‘save’ button is pressed. This way, you can provide a smooth user experience while still maintaining flexibility in handling multiple work items. Additionally, you might explore using temporary local storage to store the entered data before saving it to the database. Hope this helps!

It’s never too late :grinning:

Check out this video. Can you use a similar approach where the quote is an “item repair” and a line item is a “work required”?

Ha, just realized the date of the post :sweat_smile: