Child Tables Not Visible in Platform Analytics Reports

AnupriyaC · ‎10-08-2025

Hi Everyone,

I would really appreciate your help with this. In my PDI instance, Platform Analytics allows me to see all child tables under the Task table and dot-walk to them while adding columns in a report. However, in my dev instance, none of the child tables under Task are visible when trying to add columns in a Platform Analytics report. What could be causing this issue, and how can I make the child tables visible in my dev instance?

In My PDI:

In MY Dev Instance:

Thanks in Advance!!!

AnupriyaC · 3 weeks ago

Hi @SebastianBarnes ,

There isn’t a direct solution for this, but I did find a workaround to bring those fields into view.

When editing the report (task_sla in my case), click on the three-dot menu.
In the dropdown, you’ll see an “Open Record” option. (This will only appear after you save the report).
Selecting this will open the par_dashboard_widget record, which contains the metadata related to the table.
Within the JSON there, you can reference additional fields using the syntax:
<reference_field>.ref_<reference_table2>.<field_on_referenced_table2>
(For example: task.ref_incident.number)
You’ll need to place it in the exact position in the JSON where you want the field to appear.

Essentially, modifying the JSON allows you to surface the field you need. You can follow the steps in the below attachment as well to understand better. I hope this helps.

View solution in original post

ThorS · ‎10-08-2025

Have you checked into the table access differences between the PDI and DEV? Also, are you aware of any role differences? I believe I have higher roles in the PDI than I do in my DEV.

Last thing I can think of is to check if there's a difference in the application scope between the child tables.

AnupriyaC · ‎10-08-2025

Hi @ThorS ,

Thanks for the reply. I have the admin role in my DEV instance and tried both Global and Scoped apps same result. It works fine in my PDI, though.

In Platform Analytics, I’m trying to access Task SLA > Task > Incident > State as a column, but it’s not showing. Dot-walking works in the filter section, just not while adding columns. Both instances are on Yokohama, and the system properties "glide.ui.list.allow_extended_fields" is true in both.

Since PDI is on Patch 1 and DEV is on Patch 6, could that be the reason? Please guide me on this.

Thanks

Anupriya C

AndersBGS · ‎10-08-2025

Hi @AnupriyaC ,

Why are you creating reports based on task table and then trying to dot-walk to incident etc.? As you should know, incident, problem and other tables are extended from task table. So it is always better to report on the actual table instead of starting from task table.

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards
Anders

Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/

AnupriyaC · ‎10-08-2025

Hi @AndersBGS,

Thanks for the response. The base table I’m using in Platform Analytics is Task SLA, and I want to display columns from related tables like Incident and Problem to show the incident number, state, and SLA breach time together.

I tried using Task SLA > Task > Incident > Number to display it as a column. I have admin access, so it should ideally work. Could you please guide me if there’s any way to make it work?

Thanks,
Anupriya