Command and view restrictions in preview

When you perform actions that modify operational and transactional data within preview, this data is stored in the database, just as it would be outside of preview. Your inventory levels and coupon redemption limits can decrease, causing confusion. Also, if you perform analytics on your data, the data created by using preview can skew your reports.

To avoid this confusion, we can exclude commands and views from running inside preview by adding them to a preview exclusion file. For example, we can choose to exclude the OrderItemAdd command, preventing items from being added to orders. When a request is made to the preview Web application a check is made by the preview adapter to ensure that the name of the command or view that is being requested is not restricted by the preview web application. The preview adapter performs this check by ensuring that the command or view does not exist in the preview exclusion file.

By default, no commands are listed in the preview exclusion file.

• Disable and enabling commands and views in preview
  The commands and views disabled in preview are determined by the preview exclusion file. Initially, this file is empty, meaning that all commands and views are enabled in preview.

Related concepts
Store preview

Related tasks
Previewing a store