It isn't really used instead of the database... the data in that file
gets loaded into the database if you tell the install routine to do
that. Usually demo data in general is used for demonstration and
testing, and in a product system you would just load the "seed" data
set and not the "demo" data set which that is part of.
-David
On Feb 7, 2008, at 12:43 PM, Branden Strickland wrote:
Wow.. You guys just made my weekend!
So what your saying is....
DemoRetail.xml is essentially used IN PLACE of a DB for ease of demo
use.
If I'm to customize my data, then I have no need for any .xml file,
but
actually store my info ENTIRELY in the database. Calling it from
the SKU
ID. Could I use the "Other" Option in place of a SKU? Just curious.
Now That I see how to set this... I'm a happy happy camper.
Thanks guys!
On Feb 7, 2008 1:30 PM, Jacques Le Roux <[EMAIL PROTECTED]>
wrote:
From: "Christopher L" <[EMAIL PROTECTED]>
Responses inline.
Mine too
From: [EMAIL PROTECTED]
While I'm on that subject, In the /pos/config/screens/default/
menu I
notice
that the variable <Button name="{SKU, another button screen call, or
something else}> I realize this is the "bridge" that the POS XUI
uses
to
connect to the actual products. I've seen articles that the "Button
name="
is related to the catalog and categories. Although I can't find out
WHERE
to find my product's ID"
To clarify. I have a pizza. A large plain pizza. It's set in my
catalog
under the pizza category. Where can I go to find out what the
"Button
name"
of that item actually is in my DB?
The button name is "sku"+productid I believe. You have to set your
products up in the db, part of that will be assigning a
productid.
When creating your product in backoffice, use a link like
https://demo.hotwaxmedia.com/catalog/control/EditProductGoodIdentifications?productId=ENCHILADASto
setup your SKUs
(ProductGoodIdentifications and Skus are the same thing)
BTW I will soon add ENCHILADAS as a POS available product...
Jacques
