AndrewEverts great share! Thank you! For those that missed the Qrew Meetup yesterday, this was a new breakthrough Andrew had with Bulk Upsert that he wanted to share broadly with The Qrew. Attendees had asked for this detailed follow up.
Qrew LegendThis is brilliant.
I was unable to attend the live meet up and look forward to the recording, but I have used what I called the user focus technique for about 15 years probably once a week in my development work. In fact I even posted a demo App in the Exchange. That technique provides a way to temporarily know the "focus" of the current user (Target Parent Record ID and Source Template) when they push the button for exactly this use case. But this GetAccessKey method of kind of cheating (shortcutting) by temporarily storing the two parameters we need to know, the Record ID of the target project and the Template ID of the Tasks in the GetAccessKey is so much simpler.
I'm a QSP, so it does require my client to be on the Business level plan, but when explaining the benefits of the Business level plan, this GetAccessKey technique simplifies these types of formula URL buttons.
Hi Mark,
I appreciate your enthusiasm around the topic. I believe I've used the technique you're referencing which if I'm correct involves a table "above" the two tables you want to connect with a single record attached to all the child records.
If that sounds right, then this approach not only has the added benefit of being simpler, but also much more efficient for performance. This is because when the operation runs Quickbase does not need to calculate the value through all the dependencies running through the relationships. Maybe your original approach is different and does not involve as many calculations, however, I believe the getaccesskey approach will still be the most efficient as it's only action is to lookup the values in the url.
