# How to remember an open transaction? **URL:** \ **Category:** Ask for Help\ **Created:** [November 5, 2023, 5:53pm UTC](https://community.glideapps.com/t/how-to-remember-an-open-transaction/67551 "2023-11-05T17:53:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![MattGlides](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@MattGlides](https://community.glideapps.com/u/MattGlides)\ **Post date:** [November 5, 2023, 5:53pm UTC](https://community.glideapps.com/t/how-to-remember-an-open-transaction/67551/1 "2023-11-05T17:53:28Z")
Let’s say that the User run’s a car rental service and uses our app for it. They input the license plate data of the car, choose the driver, and it gets stored in our data tables that that car is now rented out with the license plate and driver info. The User later gets a request for the same car, but they don’t remember that the car is rented out already. The idea is that once the User inputs the number plate, the app automatically tells them that the car is rented out and gives the User the option to cancel the rental. How do I make this happen? (This is a fringe example, just to give a better understanding.) ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [November 5, 2023, 6:26pm UTC](https://community.glideapps.com/t/how-to-remember-an-open-transaction/67551/2 "2023-11-05T18:26:20Z")
> [@MattGlides](#): > > They input the license plate data of the car, choose the driver, and it gets stored in our data tables that that car is now rented out with the license plate and driver info. Would you be storing any dates at this point? eg. Rental start and end dates? If yes, then you would use those to determine if any given car was rented out at any given point in time. If no, then you probably should 🙂 ---
**Author:** ![MattGlides](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@MattGlides](https://community.glideapps.com/u/MattGlides)\ **Post date:** [November 5, 2023, 6:44pm UTC](https://community.glideapps.com/t/how-to-remember-an-open-transaction/67551/3 "2023-11-05T18:44:56Z")
Like I said that was just an example, the actual method is more of a transaction. They open the transaction for a number plate, then it kicks them back to main screen to enable them to add more number plates if there are more vehicles for the transaction. If they re-enter the same number plate, it should pop up saying “already open transaction, finalise and close transaction?”. Currenly we track the timestamp, plate number, and driver they select in a transactions table. The cars are linked in a seperate data table with their corresponding plate number. The question is more so how do we make it so in the layout it recognises that theres already a transaction open for that number plate? ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [November 5, 2023, 11:27pm UTC](https://community.glideapps.com/t/how-to-remember-an-open-transaction/67551/4 "2023-11-05T23:27:25Z")
I’m not entirely sure if this fits your flow and structure, but I think you can use a custom form, store the number plates, and use a query to the transactions table to see if there’s an open transaction for that number plate. > [@How do I create a custom form?](https://community.glideapps.com/t/how-do-i-create-a-custom-form/25014): > > I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using [User Specific Columns](https://docs.glideapps.com/all/reference/data-editor/user-specific-columns) and [Relations](https://docs.glideapps.com/all/reference/data-editor/computed-columns/relation-column) Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…