Most (not all) table have an import process. There is a stored procedure to import and a staging table to stage the data to be imported. For Contacts it called StgContact. I would recommend using StgContact and the import stored procedure for it. The advantage is that sot stored procedure will validate the imported records which will save some headaches down the road. DIM will work but it is a bit a pain to use.

Pat Gough

Most (not all) table have an import process. There is a stored procedure to import and a staging table to stage the data to be imported. For Contacts it called StgContact. I would recommend using StgContact and the import stored procedure for it. The advantage is that sot stored procedure will validate the imported records which will save some headaches down the road. DIM will work but it is a bit a pain to use.

Pat Gough

i realize i need to expand upon my original request.

the table tciContact has a number of flag fields for document transmittal... CCCreditMemo / CCCustStmnt / CCDebitMemo to name a few. these fields seem to be missing from the import processes in sage. the table stgContact doesn't have them also .

That is correct those fields aren't in the staging tables.

If you decide to use an SQL INSERT, you can set CntctKey = 0 and a trigger in the tciContact table will get the next Surrogate Key for you. This only works if you INSERT one row at a time.

Pat Gough