AQL issue with Same cluster used in multiple archetypes in the same template in version 2.0

Specifications AQL
, , ,
1

sample_template.en.v0.t.json (190.3 KB)
AQL :
{
“q”: " SELECT c1/items[at0031]/value/value as staging, c1/items[at0003]/value/value as T, c1/items[at0004]/value/value as M, c1/items[at0005]/value/value as N FROM EHR e CONTAINS COMPOSITION c[openEHR-EHR-COMPOSITION.encounter.v1] CONTAINS CLUSTER c1[openEHR-EHR-CLUSTER.tnm.v1] where c/uid/value =‘cuid’"
}

2

Formatting may be easier for others to understand:

	SELECT c1/items[at0031]/value/value as staging, 
	c1/items[at0003]/value/value as T, 
	c1/items[at0004]/value/value as M, 
	c1/items[at0005]/value/value as N 
	FROM EHR e CONTAINS COMPOSITION c[openEHR-EHR-COMPOSITION.encounter.v1] 
		CONTAINS CLUSTER c1[openEHR-EHR-CLUSTER.tnm.v1] 
		where c/uid/value ='cuid'"

Note: The formatting above is just my example and is not necessarily prescriptive.

1 Like
3

You don’t mention what the issue is? For example an error message?

1 Like
4

we are getting the aql response as null.

5

Hi @Sravanthi_Kovi,

it would be great if you raise the issue in GitHub: GitHub · Where software is built

2 Likes
6

Hi @birger.haarbrandt
sure will do that, thank you