Forum Discussion
BlakeHarrison
5 years agoQrew Captain
There are a couple of ways you could go about this. Probably the easiest would be to switch around your process a bit. Here's how I would work through this process:
Application Changes:
Process:
------------------------------
Blake Harrison - DataBlender.io
Quick Base Solution Provider
------------------------------
- On the Assets table, add a numeric field called 'Temp Ticket'
- Create a Table to Table import using the Asset table as the Source and the Ticket Assets table as the Destination
- Filter on the 'Temp Ticket' field
- Record ID# from Assets should be 'Related Asset'
- Temp Ticket from Assets should be 'Related Ticket'
Process:
- Create a Ticket and note the Record ID#
- On the CSV for the Assets, add a column for 'Temp Ticket'
- Enter the Record ID# from the Ticket into the 'Temp Ticket' column
- If any Assets are existing, be sure to have the Record ID# for the Asset also on the CSV in a column named 'Record ID#'
- Upload the CSV to the Assets table
- Run the Table to Table Import created previously
- Clear the 'Temp Ticket' field on the Assets table
------------------------------
Blake Harrison - DataBlender.io
Quick Base Solution Provider
------------------------------
- NateKurtz5 years agoQrew TraineeThank you for this! I ended up using part of this for the solution but you lead me to it!
If it helps anyone else, what i did was.
Created the Temp Ticket Field
Created an automation to run when a new asset record is created and the Temp Ticket field is empty.
Had the automation create Ticket assets where the "Related Ticket" ="Temp Ticket" (it relates the asset automatically)
Then to keep it clean i had the automation clear out the Temp Ticket field.
This runs a bit slower however it makes it easier for my users as they would only need to create the csv and upload it.
Thanks again for the help!
------------------------------
Nate Kurtz
------------------------------