NAC Osaka prod calendar - duplicate event bug

[troughc]

This seems to only be an issue in the NAC Osaka prod calendar. When I try to duplicate an event, I get an error message.
Steps to reproduce
In list view, click to open the menu next to an event and chose duplicate event.
The event form opens. Click save as draft.
This error appears:

[AbhishekPAnil]

Bug Report:
An error was triggered by the backend when attempting to save an event as a draft.

The payload for creating the event included:
"organizers": [{"type": "Organization"}]
The organizers field was missing an entityId.

This issue occurred because the event being duplicated also had an organizer without an entityId:
Event Link
This event may also have the same issue : https://staging.cms.footlight.io/dashboard/66fa7b17eb00ea006325fc46/events/67377033ad60100064a3d351

To resolve this, I have added an additional check in the frontend to remove any organizer, person, or supporter without an entityId. This ensures that the payload for event creation or updates does not include any organizers, persons, or supporters lacking an entityId.

@sahalali I am assigning this to you,to make the correction in the Backend.

[sahalali]

The issue in the backend was that the organization/person importing from Artsdata wasn't getting pulled to CMS, instead the source URI was kept in the CMS. This was causing the issue. Now, the issue is resolved in staging.

[AbhishekPAnil]

@troughc You can test this in the PR link

[troughc]

Tested in PR: PASSED

[troughc]

The regression test is failing. Please look into this.

[sahalali]

@dev-aravind, please allow the code to be deployed until the regression test is stable. Although it looks sleek, there are some issues in the regression test. We need to keep the completed issues and wait until RT is fixed.
Please remove the RT dependency in the workflow for now. Let's add it later once stable.

[kmdvs]

The RT aren't designed for other calendars than Tout Culture... At least, not yet, since I never tested another calendar... It would be great to give my 4 accounts access to all calendars, so I can actually make appropriate changes based on what calendar IS tested. In theory, since the code-base for all calendars is pretty similar (correct me if I am wrong), and the RT use the UI, and the UI don't change that much between calendars, nothing suggests a specific calendar should pose a particular problem other than small exceptions (like clicking on an additional button to edit something, or using an additional drop-down before saving an event).

I would need specific information on what fails to investigate, and more importantly, access to all calendars for my 4 accounts in production :)

[sahalali]

I am creating a separate ticket to address this issue since the RT failure is not directly dependent on this issue.