My Hybrid Shopping List -- "Interim" Collections and Persisted Tables- Revised

During final prepping of the previous version, I botched part of the video. Corrected in this version.
====
This video is Part Four of a four-part series:

Part Four explores two functions needed to make the Shopping List work:
-- Persisted tables in the SQL Azure database to retain the current shopping cart between sessions
and
-- The Patch() command for both data insertion and data update.

We wrap up with a look at the final step: moving purchased items from the shopping cart to the permanent database tables in Access.

Part One introduces the concept of Hybrid Access/PowerApps applications and explains why Access developers need to learn more about this approach.

Part Two lets you experience the PowerApps interface, running in a browser. It explains the concept of PowerApps collections -- which can be compared to temporary, in-memory tables.

In Part Two, the emphasis is on using a collection to retrieve a mirror image of a table in the SQL Azure database to improve performance with large recordsets and minimize calls to the server for data.

Part Three explores Filtering and Searching a Collection to return the minimum number of records from that collection to the Items in a Gallery. The final step is Sorting the remaining, filtered set of records for the Gallery. Two approaches to filtering are shown and compared for verbosity and performance.