When attempting to fire a workflow action that establishes relationships to multiple items in a single field, the resulting contentlet has the items ordered differently from the received order.
Relationship ordering matters, as relationships are pulled back in order, so the results of an API call should be the provided ordering.
Steps to Reproduce
Start up the demo starter
Create a content type called Ordering Test with a Title field and a relationship field called Images that is a Many to many relationship to the Images content type
Fire a call to /api/v1/workflow/actions/default/fire/PUBLISH with the following body:
Parent Issue
No response
Problem Statement
When attempting to fire a workflow action that establishes relationships to multiple items in a single field, the resulting contentlet has the items ordered differently from the received order.
Relationship ordering matters, as relationships are pulled back in order, so the results of an API call should be the provided ordering.
Steps to Reproduce
Ordering Test
with a Title field and a relationship field calledImages
that is a Many to many relationship to the Images content type/api/v1/workflow/actions/default/fire/PUBLISH
with the following body:Oddly enough the ordering is consistently incorrect, in that it's not in the order received but always orders them the same way on every call.
Acceptance Criteria
Contentlets should be related in the order they are received
dotCMS Version
23.01, 23.09.7
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Related ticket: https://dotcms.zendesk.com/agent/tickets/113628
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response