Platform Analytics - domain separation, edit indicators or collection jobs?

[webyork]

Hi so I am testing Platform Analytics and ran the migration tool. I have hit a number of issues:

1. Domain separation - means that only global reports are visible in the visualisation library. which means over 3,000 reports are now no longer visible to our user base. I have logged a cse for this.
2. The performance analytics navigator/module is now inactive.
   1. How do you edit / create indicators and breakdowns?
   2. How do you edit / create collection jobs? I cant even see if a job has collected correctly?

Obviously with point 2 I can reactivate the module to manage these, but surely I am missing something here.

Any insight appreciated

[SEAdminKS]

You're definitely not alone—Platform Analytics (Data Visualizations) introduces major architectural and visibility changes, especially in domain-separated instances. We recently completed a large-scale migration and ran into many of the same issues you're describing.

I also noticed this thread is a few months old, so you may have found some solutions by now—but I’m trying to raise more awareness around domain separation in the context of PA and Platform Analytics. There’s just not enough conversation or documentation out there on this, and the platform behaves quite differently in these setups.

 Issue 1: Domain Separation – Reports Missing from Visualization Library

You're absolutely right—only reports in the Global domain appear in the Visualization Library post-migration. This behavior isn’t currently configurable and affects any report whose sys_domain is not global.

We faced the same situation: thousands of reports and dashboards suddenly disappeared for our non-Global users. Our solution was to use a background script to update the sys_domain of key records like:

• sys_report

• pa_dashboards

• pa_tabs

• pa_m2m_dashboard_tabs

• sys_portal_page

We moved them either to Global or a shared internal domain that our support team uses to host common dashboards.

Here’s a simplified version of one script we used:

var reportGR = new GlideRecord('sys_report'); reportGR.addEncodedQuery("sys_domain=your_source_domain_sys_id"); reportGR.query(); while (reportGR.next()) { reportGR.sys_domain = 'your_target_domain_sys_id'; // e.g., Global domain sys_id reportGR.autoSysFields(false); // Preserves created/updated dates reportGR.update(); }

This same approach works for most related dashboard/table records, but obviously use with caution—especially in production—and consider domain ownership, ACLs, and visibility impacts.

Let me know if you want the full script set we used. Happy to share.

[cofagegaeta]

Platform analytics plays a critical role in managing and monitoring multi-tenant environments, especially when domain separation is involved. With domain separation, data is isolated by business unit or client, ensuring security and compliance, but also requiring more granular analytics capabilities. Edit indicators become essential in tracking changes within each domain WaPlus, allowing administrators to audit activity and maintain accountability across separated spaces.