Skip to main content
Nintex Community Menu Bar

Code Fix: Incorrect value returns when using the Manager field as an output from the UMUser SmartObject

  • February 16, 2021
  • 0 replies
  • 16 views
  • Translate

Anelle
Nintex Employee
Forum|alt.badge.img+11
  • Nintex Employee
  • 13 replies
 

Code Fix: Incorrect value returns when using the Manager field as an output from the UMUser SmartObject

KB003067

PRODUCT
K2 Five 5.2
K2 Five (5.2) Fix Pack 28

 

Issue Description

When you use the Manager field as an output value from the UMUser SmartObject, the incorrect value returns. This only occurs on an on-prem environment using Azure Active Directory and making use of the opt-in SyncEngine.

Resolution

  1. Ensure you have K2 Five (5.2) installed.
  2. Download the K2 Five (5.2) FP28 from K2 Partner and Customer Portal.
  3. Note that this is a manual fix and will not be fixed by installing this Fix Pack, however we recommend to always install the latest available Fix Pack. You must follow the manual steps, as explained in the Considerations section below, if you want to use this fix.

Considerations

This fix is only for customers using the SyncEngine and Azure Active Directory with an on-prem K2 Five (5.2) version installed that requires the AAD label appended to Azure Active Directory users. After installing this Fix Pack, follow these steps to clear the ETL watermark and implement the fix:

  1. Add the following entry to [SyncEngine].[RepositoryConfig]
    • ConfigKey = IncludeManagerLabelForAad
    • ConfigValue = True
    • ID = [same ID as “Membership State”]
  2. Clear the “Membership State” configuration value in the [SyncEngine].[RepositoryConfig] table.
  3. Clear the “Identity State” configuration value in the [SyncEngine].[RepositoryConfig] table.
  4. Let ETL Process – no need to start a sync from scratch.

 

Did this topic help you find an answer to your question?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings