Issue with Explore Data: pyGUID Column Missing in Test Environment

User Experience
, , , , , , , ,
1

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,

2

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,

3

@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.