Forum Discussion
QuickBaseJunkie
Qrew Legend
5 years agoHow about replacing the step 1 GenAddRecord button with a call to a code page that creates a new record then displays the new record for step 2?
This way it starts out as a saved record and you don't need step 3.
There is some risk of the record being abandon without data, but it might be better because you have the rid for any subsequent actions right at the beginning.
------------------------------
Sharon Faust (QuickBaseJunkie.com)
Founder, Quick Base Junkie
https://quickbasejunkie.com
------------------------------
This way it starts out as a saved record and you don't need step 3.
There is some risk of the record being abandon without data, but it might be better because you have the rid for any subsequent actions right at the beginning.
------------------------------
Sharon Faust (QuickBaseJunkie.com)
Founder, Quick Base Junkie
https://quickbasejunkie.com
------------------------------
BradLemke
5 years agoQrew Assistant Captain
Api_addrecord also isn't an option for a variety of reasons:
I'm sure there's a hundred different ways to do what we do, many of which might even be better/faster/more efficient. What I'm *REALLY* trying to do here is figure out how to make this work this way, because the solution to this (if bulletproof) will open the doors to several other process optimizations that I've been shelving.
------------------------------
Brad Lemke
------------------------------
- Several fields are intrinsically *required*, none of which can safely have a default value set for them.
- The system is a 'point-of-sale', and so we could have multiple orders pre-abandoned per week (per user), and we don't allow deletion of records due to traceability concerns.
-
- Pre-abandonment is typically due to lack of required information from the customer or salesman (ex. purchase order#) and we can't expect every single data-entry member to memorize which accounts require what info before anything can be shipped/sold. Many don't require anything special/unusual, but the ones that do require it will flat-out refuse to pay an invoice without it.
I'm sure there's a hundred different ways to do what we do, many of which might even be better/faster/more efficient. What I'm *REALLY* trying to do here is figure out how to make this work this way, because the solution to this (if bulletproof) will open the doors to several other process optimizations that I've been shelving.
------------------------------
Brad Lemke
------------------------------