Commerce Server 2002 SP2, Windows Server 2003 SE.
We were editing a product in one of our catalogs. We changed the pre-ordered
option from False to True and Saved. Looking at the Product Variants after
this change we noticed that the price for each variant had reverted to 0.00.

We thought this maybe because the Default Price was set to 0.00. On playing
around with this we have found that sometimes if the Default Price is set
explicitly (to any value) then the price of each variant remains as it
should. Other times it would not remain. Is this a known bug? Is it fixed in
SP3 or FP1.

Any ideas?

Many thanks

[ Post a follow-up to this message ]

Jake,

I've seen this problem before but it's been a while so I don't feel I can
speak authoritatively, but here's what I remember. I think what happens is
that when a product family is edited, the variant prices revert to the value
stored in the OriginalPrice field, which is populated with cy_list_price at
the time the variant is created. The behavior is there to manage the price
when products change from "indirect pricing" (where pricing is based on a
products association with a pricing category) back to direct pricing (where
pricing is based on the product's own price). See the topics "Using Current
Product Prices vs Original Product Prices" and "Product Pricing Methods" in
the Commerce Server documentation for more information. We never used
indirect pricing, but it seems like maybe some other conditions trigger this
behavior.

--
Zoe Hart
Commerce Server MVP

"Jake" <Jake@discussions.microsoft.com> wrote in message
news:FD1BF462-0B69-4D3D-B6A3-7AF50FDD5BA5@microsoft.com...
> Commerce Server 2002 SP2, Windows Server 2003 SE.
> We were editing a product in one of our catalogs. We changed the
> pre-ordered
> option from False to True and Saved. Looking at the Product Variants after
> this change we noticed that the price for each variant had reverted to
> 0.00.
>
> We thought this maybe because the Default Price was set to 0.00. On
> playing
> around with this we have found that sometimes if the Default Price is set
> explicitly (to any value) then the price of each variant remains as it
> should. Other times it would not remain. Is this a known bug? Is it fixed
> in
> SP3 or FP1.
>
> Any ideas?
>
> Many thanks
>

[ Post a follow-up to this message ]

I suppose this was fixed in SP3
http://www.kbalertz.com/kb_842086.aspx
http://www.kbAlertz.com/Feedback.aspx?kbNumber=832248

Thanks
Vinayak Tadas
Microsoft
http://blogs.msdn.com/vinayakt

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Get Secure!  For more info visit http://www.microsoft.com/security.  Please
reply to the newsgroups only


--------------------
Thread-Topic: Issue setting pre-ordered value
thread-index: AcW3kIfcXyNKu358R+eA3ugGAjUo4g==
X-WBNR-Posting-Host: 212.42.178.73
From: "examnotes" <Jake@discussions.microsoft.com>
Subject: Issue setting pre-ordered value
Date: Mon, 12 Sep 2005 04:53:03 -0700
Lines: 15
Message-ID: <FD1BF462-0B69-4D3D-B6A3-7AF50FDD5BA5@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.commerceserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:3405
X-Tomcat-NG: microsoft.public.commerceserver.general

Commerce Server 2002 SP2, Windows Server 2003 SE.
We were editing a product in one of our catalogs. We changed the
pre-ordered
option from False to True and Saved. Looking at the Product Variants after
this change we noticed that the price for each variant had reverted to 0.00.

We thought this maybe because the Default Price was set to 0.00. On playing
around with this we have found that sometimes if the Default Price is set
explicitly (to any value) then the price of each variant remains as it
should. Other times it would not remain. Is this a known bug? Is it fixed
in
SP3 or FP1.

Any ideas?

Many thanks

[ Post a follow-up to this message ]

Hi Vinayak

The symptoms in KB832248 looks like the same behaviour we are getting. I
will have to check out SP3 and get back to you.

Many thanks

Jake

[ Post a follow-up to this message ]