I have implemented an Advanced Search using a Data Page sourced from an external system, everything is working fine, except that the radio buttons to select the item from the table are disabled. I cannot figure out why that’s the case.
Typically we see that when something isn’t configured correctly. Without seeing some of the configuration it is hard to tell:
Did you create the data reference in Case Designer? Not from the property rule ground up in dev studio? You’d see this if the field was setup as “query”, maybe something changed on the property record that makes Constellation think it is a query?
Does the data object have a single page and list page Data Page backing it? This is required in Constellation in a lot of contexts (one to find the records, another to lookup each record)
Is the datapage querable? ( Allow query using a JSON object (recommended for queries using many fields) checked)
Assume you have not inadvertantly selected “read only” in the View authoring?
This is one that would need a detailed look at your configuration - it may be worth raising a Support Ticket for this so they can checkover your config to see why the selection is disabled.
If you find out please share, will help those in the future looking too
I tried to follow the articles that are available. The only thing I changed is the source of the Data Page not being an API but an activity as I need to call MQ.
I think I created everything properly. There is both a list and a single page Data Page. I created a wrapper Data Page for retrieving the items based on the search criteria, the way it is described in Pegasystems Documentation
The data page is queryable.
The view is not read only as I can enter the search criteria and I get results, I just can’t select an item.
I was trying to avoid opening a Support Ticket, but I guess I will have to.
I had a similar issue for one of the project. I noticed the DataPage lookup was mapping to the wrong Primary key. Once I changed, then it fixed the issue..