You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: FOR INTERNAL USE ONLY. For support questions, please use the EDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Currently, a user can assign a Primary Affiliation from the Contact Details Primary Affiliation fields and the Account name displays as expected with no error, even though the Affiliation record created is for the Type the Account is assigned.
What is the expected behavior?
I expect the system to throw an error when attempting to assign a Primary Affiliation with an account that does not match the Account Type.
What is the motivation / use case for changing the behavior?
When a user is creating Primary Affiliations through the Contact Details, it's reflecting incorrect information.
Acceptance Criteria
Given: I am on a Contact Details page
When: I assign an account a Primary Affiliation in-line through the Contact Detail Fields
Then: I should only be able to assign an account that is that field's specific Account Type
The text was updated successfully, but these errors were encountered:
Note: FOR INTERNAL USE ONLY. For support questions, please use the EDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Currently, a user can assign a Primary Affiliation from the Contact Details Primary Affiliation fields and the Account name displays as expected with no error, even though the Affiliation record created is for the Type the Account is assigned.
What is the expected behavior?
I expect the system to throw an error when attempting to assign a Primary Affiliation with an account that does not match the Account Type.
What is the motivation / use case for changing the behavior?
When a user is creating Primary Affiliations through the Contact Details, it's reflecting incorrect information.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: