Expand my Community achievements bar.

SOLVED

Adaptive Form behaving weirdly in different user's respective AEM Instance

Avatar

Level 7

Hello Team,

I have created an AF using FDM and when tested in my AEM Instance it was working fine as expected. So since it has to be shared with all team member's, I have created a package of same and included all dependencies in the CRX package as follows:

/content/forms/af/<formName>
/content/dam/formsanddocuments/<formName>
/content/dam/formsanddocuments-fdm/<fdmName>

I build and shared with one of my team member, it was successfully installed in his instance. Since same FDM (including Data Source and DB Configuration) and Form are used, it should behave in the same way as it was in my system. But to my shock, the behavior is completely different from my system. There are some Rules written at Root Panel Initialization level and seems like they are not working in his instance properly.

I am really confused as to why it was behaving like that, when same code / conf is used without any changes and also we both are running on same AEM Instance Version and every configuration is quite Identical.

Please let us know if any particular steps need to be followed while deploying the Forms Package from one instance to another. I was referring to this document

Adding few experts for quick resolution

@GirishBedekar , @Mayank_Gandhi , @kautuk_sahni 

Regards,

Sri Bhargav

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee

I typically recreate the datasource with the same name in the configMgr on the other instance, and from my author instance create a package to include the AF, FDM, and the  data source under /conf/global/settings/cloudconfigs/fdm and then deploy the package on the instance you want to

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

I typically recreate the datasource with the same name in the configMgr on the other instance, and from my author instance create a package to include the AF, FDM, and the  data source under /conf/global/settings/cloudconfigs/fdm and then deploy the package on the instance you want to