Logged In Username Incorrect

  • 16 February 2021
  • 0 replies
  • 5 views

Userlevel 5
Badge +20
 

Logged In Username Incorrect

kbt133630

PRODUCT
K2 blackpearl 4.7
K2 smartforms 4.7
BASED ON
K2 blackpearl 4.7
TAGS
K2 Object Browser
SmartForms Designer
Controls
Rules
SQL
SmartForms
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.
LEGACY/ARCHIVED CONTENT
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.

Issue

K2 SmartForms is returning the incorrect username when using the K2 Context Logged in Username to populate a data label with. 

Symptoms

User details incorrectly returned, this however only returns an incorrect username for some of the users and not all users.

Resolution

This resolution was a combination of two solutions:

  1. The expression used to trim down logged in users system name was altered to use a replace instead of trimming it from the sides Example: Replace(SystemUserName, TextToReplace, [EmptyString]).
  2. A new feature that was shipped for 4.7 had to be activated.
Features Purpose:
  • This feature changes the way K2 query's results from AD and did resolved the majority of the issue.
Feature Activation:
  • From the [HostServer].[SecurityLabel] Table in SQL the RoleInt was altered and the "TranslateWithDirectoryServices=False;" had been added to activate the feature as it is deactivated by default.
Why would this be needed:
  • Something changed on AD - perhaps an AD migration was done or some users details had changed, or even AD specific permissions for the K2 service account had been changed.

 

 

This feature was shipped with 4.7 and will not work in any K2 versions pre 4.7

 


0 replies

Be the first to reply!

Reply