Prefix overlap between Canada and USA

[Tyson McCarney]

So this is more of an alert to Canadians that are using or thinking about using this platform. It looks like the sample_prefix_timezone table is set for USA but there is at least one prefix I have found that is shared between Canada & USA, "250" used by small town in Alaska and most of the province of British Columbia. When importing sample with British Columbia numbers they were being coded as America/Adak which makes sense since the prefix table is not set to use in Canada. This was causing callback issues and a bug when specifying an appointment time range (drop downs were showing empty). I'm unsure if there are any other area codes that are shared or if this is just an odd case. I really like this feature though and i will be updating the table to cover all of Canada, maybe add in a country code option based on a sample attribute to allow for overlaps as defined by the supervisor who imports the sample.

[Adam Zammit (adamzammit)]

Thanks for this Tyson.

Currently to manage this - I would suggest not loading the queXS_US.sql file which contains the US prefixes, unless you are located in the US. It would be great if you could contribute an equivalent Canadian list.

If you are calling across multiple countries, then the system would need to updated to accommodate this.

One user tried this:

- empty the sample_prefix_timezone table
- empty the sample_state_timezone table
- empty the sample_postcode_timezone table

- load custom values in the sample_state_timezone table, that will be known in your sample, eg:

val,Time_zone_name
---,--------------
VIC,Australia/Victoria
NSW,Australia/NSW
WA,Australia/Perth

- Make sure your sample file contains a column with a matching "val" record

- When importing the sample, assign that column as type: "State"

The matching timezone will then apply to the record.

Adam