Sage 100

While updating the embedded io for a client on 2017 Premium (thanks @NicoleRonchetti ) I discovered the CM_Log has no unique keys!! See attached for screenshot. Any ideas on what might have caused this and how to fix it? Since they are SQL, can I just update the keys, or is it something much more sinister? This client has Premium DFDM, and sure enough, looking in there only 1 of 203 records showing in SQL shows up. Amazing that their customizations even work! **UPDATE: I went in and edited they Key in CM_Log and everything seemed to be fine, but then when I updated the panels and rebuilt the customizer log it went back to every record in the KPRIMARY being 0000001. Anyone? Buehler?

Hmm I didn't think CM tables had any embedded IO to update but at least you ran into this and get to fix it :) The amazing part you mentioned is because Customizer doesn't actually use the SequenceNo from KPrimary to load screens. It uses the 3 other indexes (alternate keys) for that purpose. The error msg indicates the dictionary is correct so I think this sequence of steps should work in SSMS: `use MAS_SYSTEM` `select * into dbo.CM_Log_Bak from dbo.CM_Log -- backup CM_Log ` `truncate table dbo.CM_Log -- delete all rows from CM_Log. Either this or Reinitialize Data Files` `-- Rebuild Customizer Log from Custom Office / Main -- this will repopulate CM_Log with the incrementing sequence numbers`

I'll try that, thanks @AlnoorCassim

Wanted to update on this in case anyone ever happens on it again. I ended up using the Reinitialize Data Files in Sage (the SQL select did not work) and doing a manual reinit on the CM_Log for each company code. I also went into the File System and removed any lingering customization in the ###-### folders that didn't apply anymore (i.e. ###-TST). Then... (not sure if this was needed) I reran the io rebuild on CM and SYS, mostly because I was frustrated and ready to feed their server to bears. But it fixed it and no bears were harmed in the fixing of this database. Thanks @AlnoorCassim!!