-
Type:
Bug
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: 2.1.0
-
Fix Version/s: 2.1.1
-
Component/s: Digital Merchandise Management → Options
-
Labels:None
-
Git Pull Request:
Steps to reproduce
- Startup 7.1 FP17 + Commerce 2.1 lpkg on SQLServer 2017.
- Navigate to Control Panel > Commerce > Products > Options
- Create a new Option Template, fill in the Name and Description
- Select Text Field or Numeric field types
- Enable all toggles including SKU Contributor.
Expected result
If a field type cannot be a SKU Contributor:
- The system should not create the Option,
- The system should display an error message
- The system should not have console errors
Actual result:
The system does not create the Option,
The system displays an error message
Console errors are as follows:
2020-04-07 23:40:40.144 ERROR [http-nio-8080-exec-7][EditCPOptionMVCActionCommand:112] com.liferay.commerce.product.exception.CPOptionSKUContributorException com.liferay.commerce.product.exception.CPOptionSKUContributorException
Creating an Option with a Text Field and SKU Contributor disabled does not throw console errors and the Option is created successfully.
Reproduced on
Tomcat 9.0.6 + SQLServer 2017 + 7.1 FP17 + Commerce 2.10 lpkg GIT ID 4b791d90a3f7704ae442b6f18d50d09552f760dc
- is related to
-
COMMERCE-2895 Can't generate SKUs if Option Field Type is a boolean
-
- Closed
-
-
LRDOCS-7665 Specify which product option field types can be used as SKU contributors
-
- Closed
-