Reference Table with Dynamic Validation
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
Contents
Case Study
- We are doing this as a prototype for an E-ticketing system.
- We are going to create a Reference to a Table in the database.
- The Reference are created for the field ET_TripBegin (Origins) and ET_TripEnd (Destinations) from table ET_Booking. They will access the Table called ET_Vehicle that is a holder of available routes or schedule trips.
Steps
Table and Column Setting for Vehicle
- The ET_TripBegin field Reference is set to Table instead of String. A new Reference 'Departures' is created. You can do that on the fly by right-clicking on it and select Zoom.
Reference Table Validation Setting for TripBegin Field
- The table is selected here and the field chosen is the ET_Departure which becomes distinct origins during pull down.
- You can see the result from the following screen.
Booking Window Result
- It shows all the available origins that the user can choose from.
- Now we shall do the same for the other field which concerns destinations or arrivals.
Table and Column Setting For Booking
- This second field ET_TripEnd will refer the same table. Note that it has an extra duty under Dynamic Validation.
Reference Table Validation for TripEnd Field
- The pull down will show all the arrivals. But we do not want all of them. We just want those that correspond to the origin.
Dynamic Validation SQL Code
- Dynamic Validation allows for SQL injection, where we supply the WHERE clause.
- Here we ask it to access the ET_Vehicle table for records similar to the origin by ensuring similar ET_Departure values.
- @..@ traps the field value in play. We place it within single quotes '@..@' for SQL to take it as a string value.