Hi Markus,
First thing, like René wrote, make sure you have a single Product entity to
create a master product list. All the documentation and attributes will be
linked to this one. Product availability is not merged with product
documentation.
I usually solve this kind of problems by creating
Hi Barry,
that page in the wiki should hold all needed info:
https://wiki.wocommunity.org/display/WOL/Install+WOLips+with+Eclipse+Update+Manager?src=search
jw
> Am 29.09.2015 um 19:50 schrieb Barry Starrfield :
>
> A basic question - how do I install the 4.4 version of WOLips in Eclipse
> Ma
A basic question - how do I install the 4.4 version of WOLips in Eclipse Mars?
This is the first time in a decade that i’m working with WO, and the current
documentation on the site seems a bit out of date. Can anyone provide
instructions?
Thanks,
Barry
__
Hi Markus,
this is a common design issue then content management meets product databases ;
-)
Generally, there are two possibilities:
1. Region centric
2. Product centric
In option 1. you assign products to a region.
Pro: each region can be setup individually ( and independen
Hi WOnderers,
I am in need for some coneptual modelling advice. Let me try to explain what I
want:
I am working on a product database application. Each product has a couple of
attributes like product code, name, etc. For each prodcut we also have a set of
electronic documents like spec sheet(s
