Occasionally you may run into a situation where you realize you either imported Product Requests into the system with the incorrect category, or created a new Style Guide and now need to move a batch of Product Requests from one Style Guide to another. Under Actions menu on the Style Guides page, there is an action called “Retrigger Mapping” that pulls together all Product Requests where their Category no longer matches their current Style Guide. You can read more on the Retrigger Mapping and other Style Guide actions here.
There are some cases in which you may notice that a Product Request is not available under the retrigger mapping bulk action. There are a few possible reasons for this including:
Product Request Imported without Category Property
If a Product Request is imported without the Category product property into the system, the Product Request will not be available under the retrigger mapping action.
Product Request Imported with Style Guide Name Category
If a column is included for Style Guide Name within the product data when creating a job, the system will prioritize this value over category data when mapping the Product Request to a Style Guide. Product Requests imported with the Style Guide Name property will not be available under the retrigger mapping bulk action.
Product Request Imported with Category but not Mapped to a Style Guide
If a Product Request is imported with a category that is not added as a category trigger on any active or available Style Guides within the system, the Product Request will not be available under the retrigger mapping action and will need to be manually overridden once the category is updated or the category assigned to the Product Request is added as a Style Guide category trigger.
Product Request has been Manually Overridden
If a Product Request has been manually overridden via Edit Product Request (see below) at any point after it was imported, it will no longer be available under the Retrigger Mapping action.
