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
Describe the bug
Within Summit Events we configure State values using native Salesforce field dependencies. But we are noticing we may have reached limits with that and creating inconsistent values for countries not the United States of America and Canada. In some cases, we are seeing US or Canadian provinces showing on unrelated countries, like Bermuda or the Bahamas.
To Reproduce
Steps to reproduce the behavior:
I was able to replicate the behavior in a scratch org.
Select a variety of countries, not the United States or Canada and you will see the same values displayed in the State/Province list and not connected in the Field Dependencies.
Expected behavior
The country does not have any values in the State/Province field and the field is not required.
Desktop (please complete the following information):
Testing on a desktop.
Additional context
It hasn't been a huge issue as the vast majority of registrants have been in the US and Canada and we haven't noticed any issue with the predefined, dependent values.
The text was updated successfully, but these errors were encountered:
Describe the bug
Within Summit Events we configure State values using native Salesforce field dependencies. But we are noticing we may have reached limits with that and creating inconsistent values for countries not the United States of America and Canada. In some cases, we are seeing US or Canadian provinces showing on unrelated countries, like Bermuda or the Bahamas.
To Reproduce
Steps to reproduce the behavior:
I was able to replicate the behavior in a scratch org.
Select a variety of countries, not the United States or Canada and you will see the same values displayed in the State/Province list and not connected in the Field Dependencies.
Expected behavior
The country does not have any values in the State/Province field and the field is not required.
Desktop (please complete the following information):
Testing on a desktop.
Additional context
It hasn't been a huge issue as the vast majority of registrants have been in the US and Canada and we haven't noticed any issue with the predefined, dependent values.
The text was updated successfully, but these errors were encountered: