We created one reusable Content Fragment Model (CFM) in a common project(A) and tried to reuse it in another project(B). While trying to read the Content Fragment Model field of A using a persistent query created inside B, it shows an error message like below:
Wondering if anyone faced the similar problem and was able to fix it?
Topics help categorize Community content and increase your ability to discover relevant content.
Did you check, if the issue related with Access / Permission issue?
Service User
Check Permission
or
Check the Query and CFM path
Is this CFM working fine in Project A?
Yes, the query is working fine if I create the persistent query in A and try to read the CFM fields created in A. The issue is only when we try to read CFM created in B from a persistent query created in A.
Hi @SureshDhulipudi, The publisher instance is free from authentication. From Project A, I can read all the fields of CFM created in Project A. The issue is with access to CFM B from a persistent query created in A.
Did you try to access or query from project A. If it works, for sure it is permission issue on fragment model and /content/cq:graphql
Yes, the query is working fine if I create the persistent query in A and try to read the CFM fields created in A. The issue is only when we try to read CFM created in B from a persistent query created in A.
Do u just mean two different sites like /content/sitea and /content/siteb, when you referred them as projects or do u actually mean two different frontend apps ? Also this could be an issue depending on the level of ur conf folders i.e. if these 2 projects use /conf/project-1 and /conf/project-2 or /conf/parent/project1 and /conf/parent/project2, then there is an issue before aem 6.5 sp17 that can even break the overall graphql functionality. More details are appreciated. Thanks !
By two projects I mean conf/A and conf/B. When I create a persistent query in A, I can't read the fields of CFM created in B.
@Mukesh_Kumar_Co Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.
Views
Replies
Total Likes
Sure @kautuk_sahni. I'll share the solution with the community if find anything.
Views
Likes
Replies