Sage 100

I asked within the following article and received one or two replies. (https://90minds-com.socialcast.com/messages/22634517) The original issue has been ongoing for about 6 years and the client has had enough. The client has lost confidence in Sage100. They are now owned by a new corporate entity and have the resources to change software and likely corporate will put pressure on them to do so. The issue is every month we have additional cost tiers show up on lot items. The layers are a duplication of a tier but the tier type is blank. I have been through multiple versions and each version continues to have the issue. Multiple resellers have had the issue but Sage says each time they were not aware there was an issue and we can't duplicate much less determine what process is generating the additional record. Anyone have the issue and found a solution?

They know about it. There's a KB article 105303 and I've emailed them but didn't get anywhere. https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=70886&sliceId=1&cmd=displayKC&dialogID=189084&docType=kc&isLoadPublishedVer=&stateId=189089&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

If they have Alerts & Workflows you could set up an event to monitor any records written to IM_ItemCost that are missing the TierType. if you immediately knew the time the record was written you could narrow down the transaction that created it. If the bad record occurred in a sales journal update you could try and re-create the transaction in a test company. Alternatively, you may be able to get a similar result by installing SQL and creating a linked server. You could create/replicate the IM_ItemCost table in SQL and have it update periodically. Have a trigger on the IM_ItemCost table to monitor for newly added bad records. Have a log file that records the date and time the records were discovered. Because of the sync, this would be an inexact science but you could get a range of times the bad record was added and may be able to narrow it down to what transaction created it. Seems like a lot of work but if the client is one you want to save it may be worth the effort.