


I am unable to create group with profile properties using repository initialization
I am testing on AEM 6.5.11 instance
below repository initialization script:
create group repo_group
set properties on authorizable (repo_group)
set givenName to "Repo Group"
end
repo_group created but profile property givenName is not adding,
getting below error:
I am referring https://sling.apache.org/documentation/bundles/repository-initialization.html document.
could you please any one suggest me on this issue
Views
Replies
Sign in to like this content
Total Likes
Hi @venkateshk87129,
Your code will not work correctly on AEM 6.5.11 or even 6.5.12, because AEM is using old version of Apache Sling Repository Initializer which is 1.1.28. Base on following ticket SLING-10192, but also looking into implementation authorizable function is available from version 1.1.36.
You can check detailed differences on github:
Solution
create group repo_group set properties on authorizable (repo_group)/profile set givenName to "Repo Group" end⚠️Please contact Adobe before you will upgrade bundle version - to make sure it will not break anything. I did very quick test, and after manual upgrade all bundles were in Active state and AEM seems to work correct and stable. Nevertheless I did not made any extensive tests, so be very cerful if you decide to follow this option.
Hi @venkateshk87129,
Your code will not work correctly on AEM 6.5.11 or even 6.5.12, because AEM is using old version of Apache Sling Repository Initializer which is 1.1.28. Base on following ticket SLING-10192, but also looking into implementation authorizable function is available from version 1.1.36.
You can check detailed differences on github:
Solution
create group repo_group set properties on authorizable (repo_group)/profile set givenName to "Repo Group" end⚠️Please contact Adobe before you will upgrade bundle version - to make sure it will not break anything. I did very quick test, and after manual upgrade all bundles were in Active state and AEM seems to work correct and stable. Nevertheless I did not made any extensive tests, so be very cerful if you decide to follow this option.
thanks you Lukasz, its working , I think adobe preferable approach is repoinit , if we get any issue using repoinit we get help from adobe support team