Push (Remove) is not working with multilingual and unique fields

[erickgonzalez]

Parent Issue

No response

Problem Statement

When trying to remove content from a receiver instance (by using the option Remove on the PP), it fails when the content has multilingual content and unique fields.

Steps to Reproduce

1- Create a Content Type with a text field and mark it as Unique. 2- Create content in multilingual (versions in English and Spanish). 4- Add content to a bundle 5- Download the bundle by using the option Unpublish 6- Upload the bundle to this same instance 7- Get an error:

Failed to publish because an error occurred: An error occurred when processing Contentlet in '/data/shared/assets/bundles/01J3JH9Y2519VE0TSCSK6FCNEY/live/test.com/102/canada/news/0-content.19287bd0-0fc1-4ffa-9622-dcea1cd14dac.content.xml' with ID 'd16eb277fe7295a2b7c7f7e5922bb443': 'Lucene query [ +structureInode:3b0620a9-6593-4999-ad4f-e907ef86385b +languageId:102 +(CanadaNews.urlTitle_sha256:a47478cd2f3e02762f4b5c963262caadc067c1728c306e6c29cd35911f25dc2d ) ] matched existing content with ID 'd16eb277fe7295a2b7c7f7e5922bb443' / inode 'abdb583e-f411-49c1-aa17-119e71b3ba6f' in ES Index, but it was not found via API. Unique fields: urlTitle [da02b43b-5806-4f42-a40f-7812c3939423], '

Note: Steps 4 to 6 are to avoid setting up PP, but to test PP, just PP the content and select the option Remove.

Acceptance Criteria

Should remove content successfully.

dotCMS Version

24.04 and master (but probably all LTS versions).

Proposed Objective

Customer Support

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.zendesk.com/agent/tickets/117241

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[wezell]

@freddyDOTCMS @john-thomas-dotcms @dsilvam

Can we QA this issue with the new unique field functionality?

[dsilvam]

Sure @wezell