[MGNLUI-6502] Submodels should not be renamed when nodeNameProperty is configured Created: 08/Jan/21  Updated: 08/Jan/21

Status: Accepted
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 0.45h
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-6334 Behaviour of node name in new framework Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Steps to reproduce

  1.  Create CT with SubModel
  2.  Add name property to SubModel definition
  3. Create CT and fill name property in SubModel
  4. Save CT

Expected results

  1. SubModel node name is not renamed

Actual results

  1. SubModel node name is renamed

Workaround

  1. Override datasource definition
    datasource:
      nodeNameProperty: jcrName
    

    Development notes


Generated at Mon Feb 12 09:37:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.