Forum Discussion
MarkShnier__You
Qrew Legend
5 years agoI think that would need real code on a code page.
------------------------------
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
------------------------------
- MichaelTamoush5 years agoQrew CaptainThanks Mark. What is the scenario that it autosaves due to the 'Save Parent Automatically...'? Is that only when it's truly adding a child? Or perhaps only with the Gen Add Record API?
------------------------------
Mike Tamoush
------------------------------- MarkShnier__You5 years ago
Qrew Legend
It's a timing issue. The record does not exists when you push the button so the [Record ID#] does not exist "in time".
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- MichaelTamoush5 years agoQrew CaptainThanks. I realized my confusion. I was testing my button push and seeing if the autosave would happen. However, I hadn't actually entered any information into my record, so essentially there was nothing to save. Interestingly, it turns out QB simply executes the button page and doesn't save the record. It doesn't do anything with the 'new record' at all.
I guess the 'save automatically' option only works if you have actually entered or changed any info on the parent.
Ultimately, I still have my issue because of what you mentioned, that the record ID does not exist 'in time'. I was hoping that I could use nested URL calls and have the first one save, hence creating the Record ID, then continue on. But I guess that takes actual code!
------------------------------
Mike Tamoush
------------------------------