Scheduled Export Recipients are not populated following an upgradeDescriptionA Scheduled Export which did have Recipients populated prior to upgrade, does not have Recipients populated following an upgrade. The Recipients get cleared out. This occurred after upgrading from Xanadu Patch 3 to Yokohama Patch 3.Steps to Reproduce Instance on Xanadu Patch 3Platform Analytics [sn_app_analytics_w] installed and up to date [version 5.05]Data visualizations [sn_par_vis_base] installed and up to date [version 25.3.4]1. Created three Assignment Groups and created one user for each of them since customer's groups are not OOB.2. Create a data visualization with the following details:a) Type: List - Simpleb) Table: Group Member (sys_user_grmember)c) fixed filter: Group > Name is one of test_group_1,test_group_2,test_group_3- Type in a group name and press Enter for it to separate with a commad) Add Columns: group and usere) Number of displayed columns: 5f) filter: active is trueg) Group by: group.name3. Save the visualization.4. Click 'Schedule' on the visualization to create a Scheduled Export with the following details:a) File Type: Excelb) Reoccurrence: Dailyc) Time: 00:00:00d) Omit if no records: truee) Recipients: three users created in step 1f) Subject: Odyssey Group Members Report5. Save the Scheduled Export. 6. Navigate to HI and upgrade the instance from Xanadu Patch 3 to Yokohama Patch 37. Following the upgrade, notice that the Recipients for the Scheduled Export are no longer populated.Before upgrading, I also tested to see if using the Assignment Group's sys_id instead of Name could be a workaround. - I duplicated the visualization, then changed the fixed filter to Group > Sys ID is one of (respective sys_ids of the created assignment groups)- I duplicated this second visualization, then along with the fixed filter of Group > Sys ID, changed the "Group by" to "group.sys_id"- I created scheduled exports from these two additional test visualizations, populated the recipients as above, and the Recipients were not populated on these following the upgrade Cause A fix script was released in Yokohama to reparent PAR Scheduled Export tables so they follow the same structure as the classic scheduled report exports. As part of this update, data fields related to scheduled exports, such as groups and users, were moved to a separate table. This migration was handled by the fix script "Migrate data to Email Recipients (sys_script_fix_75c5bc499fbc521006dd0127aa0a1cbb)." However, this script did not correctly copy users and groups from the old table to the new one.WorkaroundThis issue is fixed in 7.1.1 version of Platform Analytics which is compatible with Zurich family. The issue has been resolved in the current version of the fix script. For customers who have already upgraded, the issue may still persist. If a customer is experiencing this issue on a Yokohama+ upgraded instance, they can run the following script from background scripts to resolve the data inconsistency between the old and new tables. function fixPARExportRecipients() { var notifEmailGR = new GlideRecord("par_notification_email"); var notifEmailRecipientsGR = new GlideRecord("par_notification_email_recipients"); if (notifEmailGR.isValid()) { notifEmailGR.query(); while (notifEmailGR.next()) { if (notifEmailRecipientsGR.get("par_notification_email", notifEmailGR.getUniqueValue())) { notifEmailRecipientsGR.setValue("users", notifEmailGR.getValue("users")); notifEmailRecipientsGR.setValue("groups", notifEmailGR.getValue("groups")); notifEmailRecipientsGR.update(); } else { notifEmailRecipientsGR.initialize(); notifEmailRecipientsGR.setValue("users", notifEmailGR.getValue("users")); notifEmailRecipientsGR.setValue("groups", notifEmailGR.getValue("groups")); notifEmailRecipientsGR.setValue("par_notification_email", notifEmailGR.getUniqueValue()); notifEmailRecipientsGR.insert(); } } } } fixPARExportRecipients();Related Problem: PRB1917114