Display columns as links in Constellation tables with non-queryable data pages

The Challenge: Links with non-queryable data page

You’ve configured a column in a table to display as a link, but when you view it in the end-user portal, the link doesn’t appear. This issue is most common when tables are sourced from non-queryable data pages.

How to achieve this with a Non-queryable Data Page

The root of the issue lies with how non-queryable data pages function. As their name suggests, these data sources cannot be actively queried by the Table component. When a table tries to render a link, it needs to query the server to fetch the specific properties required to build that link’s URL. With a non-queryable source, this lookup isn’t possible, and the system doesn’t have the necessary information to display the link.

Solution

To resolve this, you must ensure that the necessary properties to construct the link are included directly in the data page’s response. The required properties depend on whether you are displaying case objects or data objects.

Object Type Required Properties to Include in the Response
Case Objects To generate links for case objects, make sure the data page response includes pxObjClass, pzInsKey, and pyID.
Data Objects For data objects, ensure that the properties configured to required parameters for the lookup data page (in the data-designer settings tab) are present in the response. For example ‘pyGUID’.
Assignment To generate links for assignments, make sure the data page response includes pxRefObjectKey, pxRefObjectClass and pzInsKey

By providing these key properties in the initial data load, the UI will have everything it needs to correctly render the links in your table without needing to perform a separate query.

Constellation 101 Series

Enjoyed this article? See more similar articles in Constellation 101 series.

9 Likes

Can i use embedded data instead of query or data reference and display one of my property as link.

I don’t think it works for embedded data.

I have the below requirement. It would be really helpful if anybody could suggest me a approach to display multiple cases.

  1. In a interaction , I’m creating a case let’s say it is create trip.
  2. After create trip case is resolved, i should be able to clone it for multiple dates, the dates are provided by user.
  3. So my approach is when the case is resolved, i’m displaying local action and in that a pagelist property to capture dates.
  4. post submit of local action i’m using activity to create cases.
  5. The cases are getting created in the backend but in the front end i’m unable to open.

Alternative which i tried.

1.I copied pyID,pzInskey to a pagelist property and showed that in the UI. But on click of pyID it is not opening the case, even though it’s a link.

Answer here: Display Multiple Cases which got created in constellation

I have linked to your active question on this, lets continue the conversation there.

I dont see any difference between the configuration of Queryable vs Non-queryable data pages with the above configuration. In either of the scenarios, the configuration mentioned above is required, isn’t it?