Issue Summary

When using third-party connect macros within the page properties with a lot of a pages across multiple spaces, the page properties report will sometimes return results from different macros.

Steps to Reproduce

1. Create a new space
2. Create a page within that space, containing a page properties macro with a third-party macro as a value. You can use the Aura - Status macro as an example, but it works with any dynamicContentMacro that makes use of the getMacroData function to retrieve the data.
   Make sure to give your page a label, as labels are required for the page properties report macro if you want to aggregate data across spaces.
3. Copy the page one time and update the macro configuration, to ensure that two different configurations exists in each page properties macro.
   Make sure that this second page has the same label attached to it.
4. Then, copy the two pages several times. The error only seems to appear when using a lot of pages.
5. Duplicate the space
6. In a third space, use the page properties report macro with the label from the second step configured
7. Go through the results and compare same with the original properties set on the page - you can use the link to the page in each row to quickly access the page

Expected Results

Page properties report macro shows the correct status for all rows.

Actual Results

Page properties report macro shows the incorrect status for some rows

Workaround

This issue occurs when pages are copied or created from a template, as the _parentId is incorrectly inherited from the original page. To resolve the problem, the customer can open the affected macro in regular edit mode and save it. This action will assign a new, correct _parentId to the macro.