Sage 100

Posting this in Sage 100 and Sage CRM. Customer is on v2016 Sage 100 Adv with Sage CRM Integrated. Customer tried CRM back in 2014 and it wasn't successful, tried the implementation again in 2017 and they are live since Dec 2017. When users log into CRM and launch CRM Sales Order Entry to create a quote, their accounting date in Sage 100 Master Console is a bizarre date. The customer did tell me Friday that the dates coming up in Master Console correlate to the first time the user logged into CRM (both 4 years ago and now). This date never changes for them. In Sage 100, when users log in, it is current date that shows in Master Console. My CRM Consultant doesn't feel it's coming from CRM and I as a Sage 100 Consultant feel it's a CRM issue. Maybe the Integration Engine? Not sure where to turn so coming to the real gurus in 90minds. Where does this date come from and how do I fix this? Pictures attached of computer system date of the user, Sage Master Console dates, the CRM Sales Order Entry screen (note the order date is correct, but the accounting date at the top shows 11/2014). Note also CRMMAS also shows the original login date of 2014. The 1/3/2018 date of the other CRM Sales Order Entry is the date that particular user first logged into CRM.

I would say it is in Sage 100 not CRM. CRM doen't know or care what an accounting date is. Data is in SY_Console for most of Master Console data but the date is in SY_ModuleDate based on the module. You could try changing it in Module Date Maintenance. If it doesn't keep the current date then I would think if you manually remove the users entry for the SY_ModuleDate that it would start to pick up correctly. As always backup before you delete it. This is based on the setting for Company Maintenance to auto set accounting date from system date being checked. If it isn't checked then check it first. Since you didn't say all users have the issue, I would assume it was checked.

What @ToddMartin said. Also, I've seen this happen once but they didn't have CRM. That client had both old dates in Sy_ModuleDate and getting Error 11 when browsing to certain records with DFDM. I think I renamed the file and copied mine over.

I know there were threads on this earlier. The date resorts to the last time they actually logged into Sage 100. Most CRM users never log directly into Sage. @JohnWilder do you recall this? @SageCRM

One thing you can do to verify if it's a Sage or CRM issue is; have the user log into Sage 100 today. Then go create the order from Sage CRM (just as a test). Then you'll know what is driving the accounting date. I know it was an issue on 2016. Can't speak to any later version.