PowerStore 3 Database Paths?

Hi there!

I have some specific questions about the Database in PowerStore 3 and how it's mapped and where things are stored. (And once again I re-iterate my request for a database map for this program!)

1) Is the SKU what is linking products in different database tables? Or is it the automatically generated product ID? For example - when a product is ordered - is the SKU what links this to the order page?

2) When someone is placing an order with PayPal and doesn't choose the express option and chooses to enter their name address and credit card info - where does that info go?

3) If I have Data Assist - how can I use this to customize the Administrative section of my PowerStore? For example - I want to add an order shipped checkbox to my orders screen, and I want to customize other features. How does it integrate with Data Assist?


Thanks!

Carlene

The sku is meant to be an internal reference for anyone managing the PowerStore, when you see the details of the order the items are related to the order based on the order id. The sku and item id are recorded in the details for an order so that you can make use of these details whenever referencing the order details for a particular order. When it comes to the other internal tables and how they relate to the items the id is used for this relationship and not the sku.

The users entered information for the billing details are not retained in your store, just the basic user info if they choose to register a new user at this time. The billing info is sent to PayPal for them to process, these details are not being stored. Any of the other information that is specific for the user is stored in the db on the confirm page using a store order summary server behavior.

The admin back end pages were crafted using DataAssist so you can use this to edit the pages there or add in some additional things. If you want to update your orders to add in a checkbox for shipped you would first need to ensure that you had this column in your orders table, then you can add in a checkbox form element to the udpate page and edit the update server behavior to use this new checkbox for the shipped column.

You said" If you want to update your orders to add in a checkbox for shipped you would first need to ensure that you had this column in your orders table, then you can add in a checkbox form element to the udpate page and edit the update server behavior to use this new checkbox for the shipped column."

Of course - I know how to add the column to my table. But can you please be very specific as to how I would use Data Assist to add this check box to my table and how I would use Data Assist to change variables in my site? I would like the site Admin to be changed via Data Assist. Specifically how do I sync up this PowerStore 3 with Data Assist? I know how to do a brand new site with Data Assist - but not how to work with an existing one.

Also - Is there a way that I could make the ProductSKU the ProductID? It doesn't make sense to me that there would need to be two numbers here - - we reference everything by Item Number. (And BTW in retail terms the SKU and the Item # are also two different things. A SKU is usually a long number that is on a bar-code and is used with most retail POS systems. An Item # is what is usually the shortened version of the SKU and is usually what is used by most manufacturers to reference all of their products in their catalogs.) I would like what you are calling ProductSKU to be the ProductID aka Item # and it not be automatically generated - but be what I am am entering in that field and for that to be the table's Key.

The db structure is very specific for PowerStore and altering how the tables relate via the SKU and product id would be a huge and difficult undertaking. This would require you to essentially rewrite not only the db structure but how all of the queries, inserts, updates, and recordsets for both the front end and the administrative back end work.

If you have the shipped column in your table you would then open up the orders_update page and add in your checkbox to the existing update form. Once this checkbox is in place you can set it's default value by selecting the checkbox and going into the property inspector and selecting the dynamic option. In here you can choose to have the box checked based on the newly added column from your table.

This will give you a checkbox that defaults to the value that is in the column for that order. Next you will edit the DataAssist Update server behavior that is on this page by double clicking it in the server behaviors tab. When the interface opens you can move to the steps where the table's columns have their values assigned. Select your newly added column and for the value use the lightning bolt icon to select your new checkbox.

This should allow you to update the new column in your table on the update page by checking or unchecking the box then updating the record.

Thanks so much for the suggestion Eric. I'll let you know how this goes when I try it.