# Issue with Explore Data: pyGUID Column Missing in Test Environment

**URL:** <https://forums.pega.com/t/issue-with-explore-data-pyguid-column-missing-in-test-environment/8962>\
**Category:** User Experience\
**Tags:** 8-7-6, low-code-app-development, theme-cosmos, financial-services, testing-applications, user-experience, constellation, senior-system-architect, pega-platform\
**Created:** [February 6, 2025, 9:33am UTC](https://forums.pega.com/t/issue-with-explore-data-pyguid-column-missing-in-test-environment/8962 "2025-02-06T09:33:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![VincenzoF17002386](https://avatars.discourse-cdn.com/v4/letter/v/22d042/32.png) [@VincenzoF17002386](https://forums.pega.com/u/VincenzoF17002386)\
**Post date:** [February 6, 2025, 9:33am UTC](https://forums.pega.com/t/issue-with-explore-data-pyguid-column-missing-in-test-environment/8962/1 "2025-02-06T09:33:58Z")

</div>

Hello,

We are currently working on a project where we are developing several case types using **Theme Cosmos**. I have encountered an issue with **Explore Data**. The `Data-` class is correctly displayed among the structures available for querying. However, the `pyGUID` column (primary key) is missing from the list of columns.

This behavior differs between the **development** and **test** environments:

- The Data Page and the corresponding Report Definition are the same in both environments.
- The column is explicitly included in the Report Definition and is not set to “Hide.”

Has anyone experienced this issue or could provide guidance on resolving it?

Thank you for your support!

Best regards,

---

<div class="post-metadata">

**Author:** ![VincenzoF17002386](https://avatars.discourse-cdn.com/v4/letter/v/22d042/32.png) [@VincenzoF17002386](https://forums.pega.com/u/VincenzoF17002386)\
**Post date:** [February 6, 2025, 9:49am UTC](https://forums.pega.com/t/issue-with-explore-data-pyguid-column-missing-in-test-environment/8962/2 "2025-02-06T09:49:00Z")

</div>

I would like to add that in the **development environment** , the issue started resolving itself without any action on my part.

In the **test environment** , I performed the following steps to make the column visible:

1. Marked `pyGUID` as a **relevant record**.
2. Saved the db table.

After these actions, the column became visible.

However, it is unclear to me why I had to explicitly mark `pyGUID` as a relevant property since it should already be treated as such by default. Additionally, I do not understand why there is a difference in behavior between the two environments. Could you provide clarification on this?

Thank you for your assistance!

Best regards,

---

<div class="post-metadata">

**Author:** ![VincenzoF17002386](https://avatars.discourse-cdn.com/v4/letter/v/22d042/32.png) [@VincenzoF17002386](https://forums.pega.com/u/VincenzoF17002386)\
**Post date:** [February 21, 2025, 3:35pm UTC](https://forums.pega.com/t/issue-with-explore-data-pyguid-column-missing-in-test-environment/8962/3 "2025-02-21T15:35:02Z")

</div>

@VincenzoF17002386 the problem was the pyGUID marked as Relevant Record but not active for the class.  
So, through the Relevant Record Landing Page, selecting the Data class, I marked as Active the property and it worked.