This Readme contains important, late-breaking information about Microsoft® Commerce Server 2002 Feature Pack 1 (FP1).
Note The Commerce Server Design-Time API Reference documentation is available as a separate help file located in the <drive>:\Program Files\Microsoft Commerce Server 2002\FP1\SDK folder, in the CS2002_AgentAPI.chm file.
This Readme contains:
The following are known issues in this release of Microsoft® Commerce Server 2002 Feature Pack 1:
Catalog Manager does not support saving a product with a list price of less than zero. Therefore, if a pricing rule results in a negative list price for a product in a virtual catalog, users will be unable to edit those products.
The Discount Migration Tool (DiscountMigrationTool.exe) expands discount eligibility requirement expressions that depend on other expressions into a single expression. Commerce Server 2002 FP1 does this since the Discount Manager application does not support inter-expression dependencies. Not all expression dependencies can be correctly expandable in a way that the user interface can correctly display them. In most cases, the DiscountMigrationTool will flag this as an error during the migration of the expressions, and then disable the discounts that depend on the expression. However, in the case of an "is-false" operator that you use to refer to another expression result, the expression will be migrated, but it will not display correctly in the Discount Manager user interface.
When you call an ASP.NET Web service from an ASP.NET application, you may intermittently receive the following error message:
"The underlying connection was closed. An unexpected error occurred on send."
For information about a hotfix package that addresses this error, see "Microsoft Knowledge Base Article 821156: ASP.NET 1.1 June 2003 Hotfix Rollup Package" at http://go.microsoft.com/fwlink/?LinkId=27665
Note This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, it is recommended that you wait for the release of .NET Framework 1.1 Service Pack 1 that addresses this issue.
The disc_id column in the discount cache in Microsoft Solution for Internet Business (MSIB) does not exist in Commerce Server 2002 FP1. This is because disc_id is a join key and may not be the same as the campaign item ID of the discount. In Commerce Server 2002 FP1 the code takes the campaign item ID of the discount from the orderlevel_discounts_applied list and performs a lookup using the disc_id column of the cache.
A NullReferenceException occurs in the MSIB 2.x site code because the following line of code does not handle the case when a lookup fails:
Change the following code in MSIB (versions 2.1 and 2.5):
private const string ContentItemDiscountID = "disc_id";
private const string ContentItemDiscountID = "item_id";
Following is a list of tradeoffs or limitations you will incur if you choose to add-on the new Microsoft® Commerce Server 2002 Feature Pack 1 (FP1) Marketing resource.
Note Commerce Server Business Desk will continue to support ads, direct mail, and List Manager. Commerce Server Manager will continue to support the existing Campaigns resource.
For example, the ads in a campaign called "Fall Sales" appear under a customer called "Advertiser ABC" and its discounts appear under a customer called "Default". Note that "Fall Sales" will appear twiceonce under "Advertiser ABC" and again under "Default".
After you migrate, the Business Desk discount is disabled and you can only create discounts in the new Discount Manager. When you create a new discount under a campaign it will be associated with the "Default" customer.
Note Customer is referred to as Advertiser in Campaign Reports.
If you create a new campaign, you must create the campaign for your ads and direct mail in Business Desk. You must create the campaign for discounts in the Discount Manager.
After you install Microsoft® Commerce Server 2002 Feature Pack 1 (FP1), you must perform the following steps to use the new Commerce Server 2002 FP1 features:
Note For detailed instructions about each step, see the "Post-Installation Requirements" topic in the "Installing Commerce Server 2002 Feature Pack 1" Installation Guide at http://go.microsoft.com/fwlink/?LinkId=24905.
Important It is highly recommended that you follow "Step 5. Update your Commerce Server Business Desk modules" in the "Post-Installation Requirements" section of the Installation Guide to update your Business Desk modules. Otherwise, your Business Desk modules will be broken.
After installing Commerce Server 2002 FP1, your site developer must perform several steps to implement Commerce Server FP1 functionality.
Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners