Hi Forum I am using portal reports in Appian 7.2. I have c

Are you seeing any errors, either in the UI (eg if you click on the clock symbol in the top right corner of the report) or in the server logs? If so please post these, and if not, can you attach a screenshot of how you have configured the fields in the 'Add/Edit Data' dialogue, showing both a variable from the sub-process that IS working, and a variable from the sub-process that is NOT working?

Hi Tom

No errors in the UI or server logs.

Here are two screenshots, showing a working appian variable called caseref and then an erroneous CDT variable client cdtClient. The caseref appears (with duplicate values per process model) on the report but the cdtClient column just has black values on the report

Hi Tom,

I've tried to create a report that includes data from the subprocess and also shows some process variables which are only applicable to the parent process model and this clears all values in the report when I try to save the report.

Hi lincolnf454, It looks like the configuration on the sub-process nodes in the main process model is not correct. If you enable "Allow data from this sub-process to be included in reports on the parent process model." on the sub-process nodes then it might work. And, please check the security on process models as well.

Hi Vinod

I noticed that the "Allow data from this sub-process to be included in reports on the parent process model." option was already checked.

I also noticed the security on the processes was differing, so I changed that and tried to run through another process instance with these changes, it still isn't picking up any CDT values

Hi everyone please ignore my second post, I have fixed this issue.

I unfortunately still am not able to expose CDT's through the "Include data from sub-processes" feature, any help would be greatly appreciated

In case you have a process and a sub process with both having PVs of same name and type you get multiple items per PV in the report. Try to use [1] to access a PV of a complex type. This would be something like pv!cdtClient[1].CLIENTNAME. There are cases this will not work consistently, but give it a try.

Thanks Stefan. Will index the first item in that case.

Still need a solution to my CDT's not being available in these reports, It's a huge issue since my build works primarily off of CDT's,