This is actually a background check process. I have a database containing a list of background check items, and I want an API to assign a result to each newly copied child record.
At the same time, I want to have a dynamic field for balance. This means that when I purchase an item from the list, the background check will be activated. As I go through the process of assigning it to a candidate, I will have a copy of the selected background check items to assign accordingly. The newly created copies will be deducted from Table 1 until the balance reaches zero, at which point the customer will need to purchase again.
you need to use make for that. Check the build it with tim video about iterating thru connected records. from there you can probalby figure it out on your own.
if you are choosing items manually from a table/list then you may want to consider using âAction Buttonâ. Screenshot is below, you can also include the arithmetic for balance tally. The action button is set to create a new record of the child (from Table 1) and inserts a copy of the child into another table (table 2). You can map the fields and copy across any field from T1 to T2
We have completed this process successfully with make vs native in Tadabase for several reasons. Conditions of what data needs to be part of the child record and the ability to get/extract the data from multiple tables as long as connections exists between the tables. We provide a complimentary 30 minute project review for Tadabase users. Please feel free to reach out at connect@rmelas.com.
For batch processing ie if you wanted to select all child records and then copy across all selected child records in one transaction then you could use Task button and set it to trigger when button is clicked ( âOnDemandâ) rather than setting it to server side daily or time/date based trigger. Youâd have to create the Task against the Table name first though, you can find this under Automation options.
Both Action button and Task button do the same job, the difference is multiple records in one step or one record at a time. As a good practice, you may want to add additional fields for transaction logs (date/time, user) to the receiving Table so you can use these fields later for traceability and for reporting purposes just incase you need that.
@Kristen , please can you set this post to âSolutionâ if @edison has a solution.
I am doing a reference check. In the settings, they can purchase a background check from the list, supposing I have 10 and they only choose to purchase 4, after this, they will have credit balance for the 4 background check they boughtâŚ
Every time they created a reference check, it uses a background check and deduct it from the credit balance. I need also a record where the background check result for that particular reference will be stored like the field saying the âdetails of the resultâ.
In the settings, I want to put a balance on how many I already used with that particular background check. and how many left.
I hope someone can help me. Duplicating it will only duplicate the entire list.
Have you tried using make as a couple folks have suggested? Or if youâre not comfortable trying that yourself you might need to reach out to one of the partners and see if someone can advise on your specific use case.
