The AddressText field is supposed to autopopulate with the concatenation of the individual fields of the address data. This works fine on the initial import when the address record is first created.
But if you do a subsequent import to update the address, and you set MFO=False so that you can just import the address fields in the CSV file instead of all 54 columns, and you leave the AddressText field blank in the CSV file, then it does NOT autopopulate with the new corrected data. It should. So the end result is that the parsed address fields get updated with the new data, BUT the AddressText field keeps the old incorrect concatenated string from the initial import!
I haven't tested this yet, but I suspect if I go ahead and explictly include the AddressText field in my CSV, that NS will then set the Override flag to TRUE since I did explictly include that field in the CSV--which is not what I want. I want Override flag to be false and the AddressText field to contain the correct concatenated string.
So I have a hunch you can't do this with CSV and have to use smbXML to get the correct end result.
I am going to test submitting a space in AddressText field in the CSV file like " " instead of null "" and see if that fools the MFO=False and causes the autopopulate to trigger and/or if the Override flag gets set to True. Update 3/15: submitting space is treated as blank by MFO so that doesn't work. See my next post. But, good news is that the Override Flag does NOT get set to True ever with CSV import.