| Alexander Yushchenko 2005-04-27, 5:52 pm |
| Ummm...
As far as I understand, we are speaking about different problems.
My problem is:
1. Products have something like "active state".
I create some custom product properties to implement this.
2. Product relations themselves also have something like "active
state".
The relation "works" only if it is active. Possibly both the source
and destanation products of the relation can be active, but the relation
itself can be inactive.
To implement this, I need some custom relation properties, but I
can't create any. 
So, the only solution I see is to make a DW extension and work
manually with it.
Are there any other solutions?
SusanH wrote:[vbcol=seagreen]
> I have no information on "Application Defined Relations". I searched on it
> in help and it looks like some kind of internal data-integrity methodology
> for the data warehouse - yikes, not something I want to play with.
>
> For relationships, I wish I knew the answer to that because I'm struggling
> with that also. What we're doing *now* is using the "Relationships" tab in
> the Product Properties (through Catalog Manager). In code, you call
> Microsoft.CommerceServer.Runtime.Catalog.Product.GetRelatedProducts() and
> that returns a DataSet of related products.
>
> However, that means that (1) each and every product has to be configured in
> Catalog Mgr; (2) you have to write code in to cycle through them, possibly
> picking out and discarding the non-Active products; and (3) it's pretty
> static and not based on real-time data.
>
> What we're trying to move *towards* is using the Predictor resource, which
> incidentally, they keep saying they don't support for Feature Pack 1. It's
> very difficult to set up, and I'm not even sure it's really what we want.
> I'd be happy to give you information about the limited amount I've found out
> about Predictor so far.
>
> "Alexander Yushchenko" wrote:
>
--
Yours faithfully,
Alexander Yushchenko
|