DOC: TableShippingADO Should Not Follow the DefaultShipping Component (217753)


The information in this article applies to:

  • Microsoft Site Server 3.0 Commerce Edition
This article was previously published under Q217753

SUMMARY

In the Site Server 3.0 documentation under the topic, "How to use TableShipping," it states:

The TableShippingADO component should always be inserted after the DefaultShipping component in the Pipeline Editor. The DefaultShipping component ensures the integrity of the OrderForm's _shipping_cost name/value pair by setting it to an initial value of zero (0). If you insert the TableShippingADO component, or any other shipping component, before the DefaultShipping component, the _shipping_cost name/value pair will be overwritten.

In fact, if the DefaultShipping component precedes the TableShippingADO component, the TableShipping component will not be executed. In order for the TableShippingADO to work, the DefaultShipping component must be removed from the pipeline.

MORE INFORMATION

The "Component Coordination" topic for "Pipeline Components" notes:

By convention, components cooperate and do not overwrite a previous component's results, unless the overwriting component is specifically designed for that purpose.

Other references in this help topic suggest that the shipping components are an exception to this rule.
Modification Type:MinorLast Reviewed:7/14/2004
Keywords:kbdocfix KB217753
©2004 Microsoft Corporation. All rights reserved.