Forum Discussion
MarkShnier__You
Qrew Legend
6 years agoYes, the process that you are describing is exactly the process I do now. It will mostly work. But if the Automation fails or if child record get created too quickly for the Automation to keep up (say a bunch of children get created by a Copy Parent Child button), then I'm looking for an overnight process to be able to create the parents. My issue is that these children may not all have unique parents, so I can't just import them into the Parent table as there may be duplicated in the child data.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
OanaWhalen
6 years agoQrew Cadet
Are you able to identify where your automations start tripping over each other? I had an app do that recently and I was able to build a 5 minute delay into a code page that checked a box to trigger the automation. This works for a manually triggered import process and slowed my very length automation process down enough to let the system catch up, though I'm not exactly sure how a code page could get called on a scheduled import.
(function(){
setTimeout(()=>alert("Please wait a few moments while your data is processed."),500);
document.body.style.cursor = "wait";
setTimeout(()=>alert("1 min remaining"),240000);
setTimeout(()=>$.get(DataImported),270000); //Delay Data Imported checkbox by 4 min 30 sec.
setTimeout(()=>alert("Data import is complete!\n\nIf you do not see all your data on the next page, please refresh the page in a
few minutes."),295000);
setTimeout(()=> document.location.href = GoToPropConditions,300000) ; //Delay screen refresh by 30 additional seconds
})();
*Code abbreviated for clarity.
------------------------------
Oana Toma
------------------------------
(function(){
setTimeout(()=>alert("Please wait a few moments while your data is processed."),500);
document.body.style.cursor = "wait";
setTimeout(()=>alert("1 min remaining"),240000);
setTimeout(()=>$.get(DataImported),270000); //Delay Data Imported checkbox by 4 min 30 sec.
setTimeout(()=>alert("Data import is complete!\n\nIf you do not see all your data on the next page, please refresh the page in a
few minutes."),295000);
setTimeout(()=> document.location.href = GoToPropConditions,300000) ; //Delay screen refresh by 30 additional seconds
})();
*Code abbreviated for clarity.
------------------------------
Oana Toma
------------------------------
- MarkShnier__You6 years ago
Qrew Legend
I suppose that a partial solution would be to import the children into the Parent table, like i do now on a scheduled basis, but to introduce a filer to only import where the Record ID# ends in a zero. That would cut down on the chance of a duplicate parent being created in to the import set (causing it to fail) by a factor of 10. Then the Automation would update a counter value to 1 and rerun the import, etc for 10 times.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------