Share via

How to Modify the Orders Configuration Files

  • Article

Four configuration files affect the behavior of the Orders System:

  • Web.config. Defines how to map addresses in the Profiles System to the Orders System, determines whether any new classes that you created replace core orders classes, and identifies limits on how many objects can be created for each user.

  • OrderObjectMappings.xml. Defines how objects in the Orders runtime map to tables and columns in the database.

  • OrderPipelineMappings.xml. Defines how objects in the Orders runtime map to entries in the dictionaries that pipelines use.

  • LanguageCode**_OrdersPresentationInfo.xml**. Determines the names to display in the Customer and Orders Manager for Orders classes and their properties.

When you create a new class that is used by the Orders System, you must modify the configuration files. If you add a new weakly typed indexer property to a core Orders class, you might also have to modify the configuration files. The following table lists the Orders configuration files and the situations in which you might have to modify each file.

Configuration file

Reasons you might have to modify

Web.config

  • Created your own class that interacts with or replaces a core Orders System class.

  • Created a new version of a class that interacts with or replaces a core Orders System class.

  • Modified the name or location of an assembly.

OrderObjectMappings.xml

  • Added a weakly typed indexer property that you want to store in a column of a database table.

  • Created your own class that interacts with or replaces a core Orders System class.

  • Created a new version of a class that interacts with or replaces a core Orders System class.

  • Modified the tables or columns of the database that Orders objects are stored in.

OrderPipelineMappings.xml

  • Created your own class that interacts with or replaces a core Orders System class.

  • Created a new version of a class that interacts with or replaces a core Orders System class.

  • Added a pipeline component that uses a property that existing pipeline components do not use.

LanguageCode_OrdersPresentationInfo.xml

  • Created your own class that replaces a core Orders System class.

  • Created a new version of a class that interacts with or replaces a core Orders System class.

In This Section

See Also

Other Resources

Mapping Purchase Orders to the Database

Extending the Orders Runtime