Hello,
I just tried this and it worked fine. The syntax of my load file:
TABLE usp_contact
id c_cm_id1 c_cm_id2 c_cm_id3 c_cm_id4
{ "016BBC2CE538094F8C77F4DF26AB3C89" ,"1800" ,"1800" ,"1800" ,"1800" }
{ "16226C765005B94E957E0F477DEF1B1C" ,"1800" ,"1800" ,"1800" ,"1800" }
{ "17DEA1027C7C3746B6F25DB6604EEE23" ,"1800" ,"1800" ,"1800" ,"1800" }
I was wondering if you could confirm if the id values you are feeding in are valid.
The following is an alternative approach to potentially addressing the problem of the data load but should only be done after you have fully backed up your existing database.
One thing I also did to reverse engineer the content being loaded was to do a full extract of all usp_contact records and modify the resultant output to update the notification methods across the board.
First, I ran:
pdm_extract -f "Select id, c_cm_id1, c_cm_id2, c_cm_id3, c_cm_id4 from usp_contact" > mod1.dat
Then I edited the generated mod1.dat file and changed the four text fields at the end of each line to have the notification methods set, and then loaded the updated mod1.dat file back in.