You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usage scenario: a user created a Multiple-Choice Matrix with a Rating column in an older version of SurveyJS libraries (v1.9.82). The user manually defined rate items.
In v1.9.82, custom defined items appear correctly: View Demo.
However, in v1.9.98, custom defined rate items do not appear by default: View Demo.
This happens because the autoGenerate:false option was not specified for a Rating Scale column. If you disable this option in a survey JSON, custom defined items will appear (View Demo):
However, it is expected that this option will be automatically disabled in a new version of SurveyJS libraries if a Rating Scale column has custom defined items.
The text was updated successfully, but these errors were encountered:
RomanTsukanov
changed the title
Multiple-Choice Matrix with a Rating Scale column - The custom defined rate items aren't enabled by default
Multi-Select Matrix with a Rating Scale column: Custom rate values aren't enabled by default
Aug 1, 2023
User Issue: T14013 - Breaking change(?) in the "Multiple-Choice matrix"question in the latest release
https://surveyjs.answerdesk.io/internal/ticket/details/T14013
Usage scenario: a user created a Multiple-Choice Matrix with a Rating column in an older version of SurveyJS libraries (v1.9.82). The user manually defined rate items.
In v1.9.82, custom defined items appear correctly: View Demo.
However, in v1.9.98, custom defined rate items do not appear by default: View Demo.
This happens because the
autoGenerate:false
option was not specified for a Rating Scale column. If you disable this option in a survey JSON, custom defined items will appear (View Demo):However, it is expected that this option will be automatically disabled in a new version of SurveyJS libraries if a Rating Scale column has custom defined items.
The text was updated successfully, but these errors were encountered: