I've run the v11 pre-upgrade check sql and we've got a bunch of country/state mismatches. Looks like most of these are where the state is blank but not null (and all from an earlier conversion.) The advised fix assigns a country based on the state. For these where the state is blank, is it kosher to set the state field to NULL? It looks like that's the default behavior if there is no state in tr_state for a country.
Yes, setting state to NULL in this case is correct.
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Brian GrahamSent: Tuesday, January 17, 2012 12:57 PMTo: Ron WilsonSubject: [Tessitura Next Generation Forum] V11_pre_upgrade_check - NULL states
You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
Hi Ron,
We do not have entries in TR_state for all possible countries with NULL values for the state. Do we need to have these entries with NULL states? We're getting 910 contacts on the code checks and some are NULL and some are blank.
Michele
Michele,
No, you do not have to add NULL states for every country. You should only need to set the blank states to NULL.
David
So David, I'd just like to confirm that for the 900 files that it's telling me have an invalid state/country value in T_Address that we just need to set the Locale to NULL in each customer record?