with reference to my earlier posts

@harshav Hi, here goes the explanation to your questions as per my knowledge:
1.Even though the CDT pv is single why am I getting multiple values in report for emp ID
When you choose the option 'Include data from sub-processes', the data starts appearing from the sub-processes in the report for the each parent process row in the report. So let's take your case as an example. Let's say you have a PV by name 'employeeDetails_cdt' in the parent as well as child processes. While creating a report, choosing the option 'Include data from sub-processes' populates the particular parent process record with the values found for pv!employeeDetails_cdt.empID from parent as well as child processes. So that's how you end up in seeing multiple values, as your configuration itself is trying to query the values from multiple (parent and child) processes. If you know that the values are going to be same across the processes irrespective of hierarchy, then you may go for applying a function such as fn!union() to refrain from seeing duplicates in the report. Further you observe this behavior only for parent processes, as they are the ones that will pull more than one value depending on the child processes it has got. You won't observe this pattern for a child/standalone process (or a process that has no sub-process node configured in it) as it just gets a value of its own context but not any other values. You may see some null values out of the multiple values being seen here, but I guess that might be because of the reason that the values aren't populated in the corresponding sub-process.

2. When I gave an indexing to the CDT pv in report how come the values are getting populated.
I would leave this to others but a wild guess is that this could be because of the casting, that is, employeeDetails_cdt[1].empID resolves to a data type which is of type single.

Re the Appian Version, to the best of my knowledge, at-least the functionality (Reporting and the configurations in it) which we are discussing here hasn't got any changes and so isn't dependent on the version.

Let's see if other practitioners could give some invaluable suggestions.

@harshav Hi, here goes the explanation to your questions as per my knowledge:
1.Even though the CDT pv is single why am I getting multiple values in report for emp ID
When you choose the option 'Include data from sub-processes', the data starts appearing from the sub-processes in the report for the each parent process row in the report. So let's take your case as an example. Let's say you have a PV by name 'employeeDetails_cdt' in the parent as well as child processes. While creating a report, choosing the option 'Include data from sub-processes' populates the particular parent process record with the values found for pv!employeeDetails_cdt.empID from parent as well as child processes. So that's how you end up in seeing multiple values, as your configuration itself is trying to query the values from multiple (parent and child) processes. If you know that the values are going to be same across the processes irrespective of hierarchy, then you may go for applying a function such as fn!union() to refrain from seeing duplicates in the report. Further you observe this behavior only for parent processes, as they are the ones that will pull more than one value depending on the child processes it has got. You won't observe this pattern for a child/standalone process (or a process that has no sub-process node configured in it) as it just gets a value of its own context but not any other values. You may see some null values out of the multiple values being seen here, but I guess that might be because of the reason that the values aren't populated in the corresponding sub-process.

2. When I gave an indexing to the CDT pv in report how come the values are getting populated.
I would leave this to others but a wild guess is that this could be because of the casting, that is, employeeDetails_cdt[1].empID resolves to a data type which is of type single.

Re the Appian Version, to the best of my knowledge, at-least the functionality (Reporting and the configurations in it) which we are discussing here hasn't got any changes and so isn't dependent on the version.

Let's see if other practitioners could give some invaluable suggestions.