Hello,

I'm not 100% sure I'm understanding your issue correctly... But, in any case, here are some notes:

Postal Codes are user-entered data and need to be accepted from users all over the world. What that means is that you can't always assume they'll be in a format of #####. Even in the US, #####-#### is still perfectly valid.

So, you need to make your code smarter. Some of this depends on your locations API - that might handle this all just fine. If not, then you'll need to pre-clean the data to find the records that you can handle. For example, you could look at US values only that have 5 or more characters and take the left five, and make sure they're numeric. If that all works, assume it's a valid zip.

Mike

Mike the format is not the problem.

Sebastian  I need the DB data in UserProfile.PropertyDefinitionID to be same number across all users.  I have custom profile as PostalCode is not available unless custom.

The first user PostalCode was UserProfile.PropertyDefinitionID=11, 2nd UserProfile.PropertyDefinitionID=34 and keeps incrementing.

Is there a DNN switch that will keep UserProfile.PropertyDefinitionID # with PostalCode constant for all users.

Unless I can solve this looks like Users.LastIPAddress and a different DB with Lat & Long so distance can be calculated is the way to go.