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
EDA Settings: When Enable Record Type Validation is true an error is thrown due to University Department Account Record Type in Affiliation Mappings
#195
Open
jacebryan opened this issue
Apr 8, 2020
· 3 comments
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?
After Enable Record Type Validation is set to True in EDA Settings, I attempt to create a Contact and receive the following error message:
A validation rule is preventing the record from being processed. This could be from this record, or a related record being updated. VALIDATION MESSAGE: We can't save this record because of an Account record type error in Affiliation Mappings. Ask your administrator to verify that Account Record Types are correctly mapped to Contact Primary Affiliations.
Looking at the Affiliation Mappings in EDA Settings, I notice that "University Department" is listed under Account Record Type for the Primary Department Contact Primary Affiliation Field mapping. Changing the value from "University Department" to "Academic Department" resolved the error.
What the Investigation Uncovered
The error is stemming from the fact that there is no University Department Account Record Type in the K12 Kit. Note: Using the API name associated with the Academic Department (i.e. University_Department) did not resolve the error.
What is the expected behavior?
Academic Department is listed under Account Record Type for the Primary Department Contact Primary Affiliation Field mapping.
The text was updated successfully, but these errors were encountered:
@jacebryan -- we are looking into this today actually. A member of the team noticed we were having some issues when Record Type Validation was enabled. We think we introduced this bug while attempting to get more flexible functionality from the record type mappings (more for multilingual purposes IIRC).
We have a spike already open. Thanks for creating an issue!
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?
After Enable Record Type Validation is set to True in EDA Settings, I attempt to create a Contact and receive the following error message:
A validation rule is preventing the record from being processed. This could be from this record, or a related record being updated. VALIDATION MESSAGE: We can't save this record because of an Account record type error in Affiliation Mappings. Ask your administrator to verify that Account Record Types are correctly mapped to Contact Primary Affiliations.
Looking at the Affiliation Mappings in EDA Settings, I notice that "University Department" is listed under Account Record Type for the Primary Department Contact Primary Affiliation Field mapping. Changing the value from "University Department" to "Academic Department" resolved the error.
What the Investigation Uncovered
The error is stemming from the fact that there is no University Department Account Record Type in the K12 Kit. Note: Using the API name associated with the Academic Department (i.e. University_Department) did not resolve the error.
What is the expected behavior?
Academic Department is listed under Account Record Type for the Primary Department Contact Primary Affiliation Field mapping.
The text was updated successfully, but these errors were encountered: