Hi All, I am facing a very strange problem, where I am using a Execute Process r

@harshav No worries. You may do so but I am sure that you are aware of the behavior of 'Include data from sub-processes' setting. So, as long as the results are yielded as desired, you may proceed. And re cdt[1].id, that's fine, I just wanted to check a possibility of the multiple type of the variable.

Re the effects of configuration, I would suggest checking the other dependent functionalities on the corresponding Portal Report object. If there are any, I would suggest mentioning them at a very high level so that myself or community can come up with some inputs.

Earlier in this post, you said that the report is working fine in Dev but is not able to do well in Prod. I would suggest investigating the root cause and draw a conclusion by analysing the deployed application's contents (as there may be a chance that the intended objects aren't moved while deployment) or the pattern among the process instances (that is, why the instances in the Prod aren't able to show up the value when the instances in Dev are capable of doing so. For instance, 'Allow data from this sub-process to be included in reports on the parent process model' might haven't been checked initially and is updated in the recent versions.).

@harshav No worries. You may do so but I am sure that you are aware of the behavior of 'Include data from sub-processes' setting. So, as long as the results are yielded as desired, you may proceed. And re cdt[1].id, that's fine, I just wanted to check a possibility of the multiple type of the variable.

Re the effects of configuration, I would suggest checking the other dependent functionalities on the corresponding Portal Report object. If there are any, I would suggest mentioning them at a very high level so that myself or community can come up with some inputs.

Earlier in this post, you said that the report is working fine in Dev but is not able to do well in Prod. I would suggest investigating the root cause and draw a conclusion by analysing the deployed application's contents (as there may be a chance that the intended objects aren't moved while deployment) or the pattern among the process instances (that is, why the instances in the Prod aren't able to show up the value when the instances in Dev are capable of doing so. For instance, 'Allow data from this sub-process to be included in reports on the parent process model' might haven't been checked initially and is updated in the recent versions.).