Defects

Dependency is not honored for multi-user fields when the independent (parent) field value changes



ID:    D27754
Published:    09 February 2021
 

Defect Id

DEF344206

Originally Reported Against

SBM 11.8 Patch 1

Status

Submitted

Description

 Example Setup:
* Create a Multi-User field called MyGroup with the Groups & Users mode.
* Use the system Item Type field and setup values: TypeA and TypeB
* On the Item Type field, set the Dependency to be the MyGroup field
* Deploy the changes.
* In the App Admin, create GroupA and GroupB
* In the App Admin, under workflows, find the MyGroup field and enable the values GroupA and GroupB
* In the App Admin, under Projects > Default Fields > Item Type > Dependencies, setup dependencies as:
   TypeA = GroupA
   TypeB = GroupB
 
Steps to Reproduce:
 1) Submit an item and change the type to be TypeA. Notice the MyGroup field value is GroupA (Good)
 2) Cancel that submit.
 3) Submit an item and change the type to be TypeB. Notice the MyGroup field value is GroupB. (Good)
 4) Now, change the type to be TypeA. Notice that the MyGroup value is now GroupA AND GroupB (Bad)
 
Expected:
When the master (parent) field is updated, any previous values should be removed from the multi-user field and only valid dependent values should be added.
 
Actual:
The multi-user field has an invalid select (dependency violation). When the item is submitted, the user will get an error:
One or more fields are invalid.
'MyGroup' has an invalid selection. Please select a valid value to complete this transition. 

Resolution

 Workaround:
Create a form action like this:
When ItemType field changes value
Then clear MyGroup field   

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs