-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 3.15.1
-
Fix Version/s: 3.22.0
-
Component/s: Content Views
-
Tags:
-
Backlog priority:600
-
Sprint:NOS 11.1.18 - 2019-09 2, NOS 11.1.20 - 2019-10 2, NOS 11.1.19 - 2019-10 1, NOS 11.1.21 - 2019-11 1, NOS 11.1.22 - 2019-11 2, NOS 11.1.23 - 2019-11 3
-
Story Points:2
A path for upward compatibility of a pre-9.1 Studio project is requested.
Since NXP-21025/NXP-18555, it is known that common:size is replaced with file:content/length and file:filename is replaced with file:content/name
However, if a valid LTS 2016 project references file:filename as Default Sort in a content view and this project is upgraded to LTS 2019, then the ERROR message:
Validation Error(s):
A sort info is using a property 'filename' that does not exist in schema 'file'.
is displayed, and you cannot select file:content/name from or file:content/length from the Studio dropdown list
Requesting an upward compatibility path to be found.
Expected:
- in content views results listing and table layouts (JSF UI dependency required), file name option should be offered for sort
- an existing project upgrading still needs to choose the new option, no automatic migration is done
- causes
-
-
- Resolved
-
