Forum Discussion
MarkShnier__You
Qrew Legend
5 years agoI would suggest that you import into steps.
The first step will just bring all the data into a scratchpad table in QuickBase where the validation will be done. Then I presume you would have a simple checkbox formula to calculate if the data is valid and you would make a button or Process to do a saved table to table copy API run import to move the data into the real table.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
The first step will just bring all the data into a scratchpad table in QuickBase where the validation will be done. Then I presume you would have a simple checkbox formula to calculate if the data is valid and you would make a button or Process to do a saved table to table copy API run import to move the data into the real table.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- DineshRampal5 years agoQrew CadetThanks Marks. I would prefer one step process, using some Java scripting OR pipeline as many users would be uploading data and hence want it to be more efficient.
------------------------------
DineshDineshdinesh.rampal@apollotyres.com
------------------------------- MarkShnier__You5 years ago
Qrew Legend
I don't see how you can have a one step process without having a way for the uploaders to deal with their rejects.
My suggested solution could allow each separate user to deal with their own rejects.
My solution would be an upload and a button click.
Also, It sounds like you would be using up a a lot of Step Runs if you are dealing with records one by one in pipelines.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------