Enable List of Values:
When a geography type is mapped to an address attribute, you can choose whether to display that geography type in a list of values during address entry in user interfaces. It's important to review this carefully, as you should only enable a list of values if you have sufficient geography data imported or created for that geography type.
Once you enable a list of values for an address attribute, users can only select from the available geography data for that geography type. This means that if a specific geography value is not present in the geography hierarchy, users cannot create an address with a different geography value.
Tax Validation:
You can also determine which geographical elements are included in tax validation. For instance, in the United States' North American address format, you might specify that the County, State, and City are used for tax validation. This means that for a transaction involving an address with the North American address format, the address must have the correct combination of county, state, and city, according to the geographical hierarchy data, to be considered valid for tax calculation.
Geography Validation:
You can determine whether a specific geography type will be included in geography validation. For example, when a user enters a United States address using the North America address format, the address must have the correct combination of country, state, and postal code based on the geography hierarchy data to be considered geographically valid. If an address element is mapped to a geography type but is not selected for geography validation, suggested values will be provided for that element during address entry, but the element itself will not be validated.
I hope this blog post was helpful for you. If you have any questions or feedback, please leave a comment below.