This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
When using the K2 Context Logged in Username to populate the username on a form, this returns an incorrect username for some users, other users works fine.
Smarforms returns incorrect logged in user
for some users.
This issue could be caused by the following:
- Something changed on Active Directory, i.e. an Active Directory migration was done, user details changed or Active Directory specific permissions for the K2 service account had changed.
- A feature that was shipped for 4.7 which had been implemented on a test environment and had been confirmed to have resolved the majority of this issue can be found below.
- This feature changes the way that K2 queries results from Active Directory. From the [HostServer].[SecurityLabel] Table in SQL the RoleInt was altered and the "TranslateWithDirectoryServices=False;" had been added.
Please log a support ticket for a support engineer to assist with applying this feature.
- An expression might be in use on the user context system name in SmartForms which could possibly be cutting off the characters in a way that the expression would not return any data anymore. Therefore the recommendation would be to validate your expression carefully and reconstruct the expression to resolve the issue if neccessary.