Last updated: Jan 29 2018
Feature-specific Commerce configurations
This topic describes available <appSettings> configuration options for Commerce.
Indicates if a promotion is excluded from being applied per order or per unit.
|AutoMigrateEPiServer||If set to true, when the site starts, the migration steps are run automatically. Otherwise, site admins must log in to the migration view and run the steps manually.|
|DisableVersionSync||Indicates if an update to catalog content done outside of the content APIs removes version data (e.g., drafts, old published versions...) for affected content.
Setting this to true can improve the speed of batch operations done through the lower-level APIs (like ICatalogSystem), e.g., the catalog import.
See also: Commerce 9 - upgrading and migration
|episerver:tracking.Enabled||Indicates if the Tracking system executes tracking.
See also: Recommendations API overview.
|episerver:personalization.BaseApiUrl||The URL of the Episerver Perform environment to be used. Should contain only the protocol and host name.|
|episerver:personalization.Site||The site name used to identify requests to the tracking server.|
|episerver:personalization.ClientToken||The token used to authenticate tracking requests to the REST API. See also: Episerver Recommendations.|
|episerver:personalization.AdminToken||The token used to authenticate admin requests to the REST API.|
|episerver:personalization.RequestTimeout||[Optional] Timeout for REST calls. The default value is 30 seconds.|
|episerver:personalization.TrackingMode||[Optional] The tracking mode to use. Acceptable values are ServerSide and ClientSide.
|episerver:personalization.CatalogFeedBatchSize||[Optional] The number of products processed in one batch when the product feed is generated. A higher value can be faster but puts more pressure on the memory. The default value is 50.
See also: Customizing exported product information.
|episerver:personalization.CatalogNameForFeed||[Optional] Selects the catalog used to generate the product feed if you have multiple catalogs. If this value is not set, the first catalog is used. See also: Customizing exported product information.
Note: This property will be removed when Product feed support for multiple catalogs is added.
For the Remove Expired Carts job, sets the number of days after the last modification before a cart is considered abandoned and removed by the job.
The default value is 30 days.
|episerver:ExpiredCartsRemovalJobExcludedCartName||For the Remove Expired Carts job, sets the cart name that is excluded from being removed by the job, even if it has not been changed for a longer time than the configured value. The default value is "WishList".|
|episerver::DataBaseIndicesJobCommandTimeOut||For the Maintenance Database Indices job, set the value (in seconds) before database requests are considered timeouts.|
|episerver::LowFragmentationThreshold||For the Maintenance Database Indices job, sets the fragmentation value (in percent) of indices. If an index's fragmentation level is below this value, it is not maintained. The default value is 10.|
For the Maintenance Database Indices job, sets the value (in percent).
The default value is 30.
Indicates whether validation of entry uri segments should be strict or not.
|episerver:commerce.UriSegmentConflictsEmailRecipients||Recipients that will get an email if any URI conflicts are found by the Find Catalog Uri Conflicts scheduled job. To specifying multiple recipients, separate email addresses by a semicolon (;).
See also: URL segment and SEO URL and Increased Flexibility in Commerce Catalog URLs.