On a SharePoint Web Application that has various Site Collections, when performing an installation of K2, the K2 Features need to be activated on each Site Collection individually. With the introduction of Claims Based Authentication, user connection strings are created on hidden lists within each Site Collection. These hidden lists are only created when K2 Features are activated correctly on the Site Collection. On a Claims Based Authentication site, when attempting to execute Dynamic SmartObjects based on SharePoint Lists or Libraries created on Site Collections that have not had K2 Features activated correctly, the People/Group properties are not returned. This is because the user cannot be resolved as the connection string does not exist.
- Create a SharePoint Web Application with Site Collection 1 and Site Collection 2
- Apply Claims Based Authentication on Site Collection 1 and 2
- Install K2 and activate all K2 Features on Site Collection 1
- Create a Dynamic SmartObject based on a SharePoint List or Library, which contains a People/Group column, created in Site Collection 1
- Attempt to execute the Dynamic SmartObject based on the same SharePoint List or Library on Site Collection 2
- The People/Group properties are not returned
It is important to note that K2 Features need to be activated on a SharePoint Web Application root or parent level as a minimum requirement.
This Hotfix is contained within the latest K2 Update. Install the update package to resolve the error.