Showing multiple order details on one page

I have a shopping cart system that pretty much follows the standard cart & checkout in eCart 5. It uses a users table, order table and order details table. I've generated all the proper backend pages with DataAssist/Data Bridge and am able to view Order Details in the backend one at a time.

My client wants to be able to click a button to load all unprocessed orders onto a single page for printing purposes, then once printed click a single verification that they have been printed OK and have all those orders 'archived'.

I know you can't give me a step by step, but can you give me some general direction on how to (A) pull multiple order/orderdetail records all on one page. The current detail page pulls it with two different queries, but that won't work for multiple orders on one page. Secondly, (B) the general approach to take every order in that result and change one field, like a 0 to a 1, to indicate the order has been processed.

Thanks. Any direction would be appreciated.

you will still use 2 recordsets for this, the key to making this work is to use a repeat region to show multiple orders and place the details recordset inside the repeat region so that it requires for each order shown on the page

your orders table would need to have a column to mark the orders as processed or.


you would create a recordset to return all orders where the processed column was set to unprocessed.

add the information to the page to show the order on the page and add a repeat region around it.

Next add the order details recordset. The order details recordset will use the OrderID column from the orders recordset as the filter on the detailOrderId column. you will need to manually move the details recordset code so that it is inside the repeat region for the orders recordset



since you are showing all unprocessed orders, you can set the updated behavior to use the processed column as the key column and update all records where processed is equal to unprocessed, to change that column to archived.

So I can query another recordset within the body, within the repeating region? I never realized that as my queries have always been in the head.

"since you are showing all unprocessed orders, you can set the updated behavior to use the processed column as the key column and update all records where processed is equal to unprocessed, to change that column to archived."

I don't think we want to simply change all '0's to '1's in the processed column. What if a new order comes in between the time of the original page query and the time they finish processing orders and verify? An order could get tagged even though it wasn't a part of the original query.

yes, you can move recordset code to be in the repeat region It will get created in the head, so you need to manually it to the repeat region.

for the update, you could create a comma separated list of the product IDS inside the repeat region and as a hidden form element. you would need to hand code the update SQL for this using:

UPDATE yourTable SET processed = 1 WHERE productID IN($_POST['idList'])

Now this looks really interesting, and I think a tutorial about it demoing how one can include record sets within the HTML is beneficial.

I did know this could be done as I have previously built a dynamic menu where it has a recordset within the html of the menu. The benefit of this was to be able to get parent, child and sub-child items within the menu and make sure they appeared in the correct place. It was complex though!

Isn't your powerstore products menu built in a similar manner? Was that built with CSS Menu Writer, or did you manually create it?

Mat

I'll forward your comment to the documentation team.

Yes, menu writer uses nested recordsets to create dynamic menus