Today was my turn at the bat… so to speak
MSDynamicsWorld’s Decisions Spring 2011 Conference is now open for attendees. Today is AX Day and I have toured through the different Expo booths and have had a chance to chat with a few known souls
In past days I released an article explaining the upcoming Named Systems Database architecture enhancement in codename GP “12″ release. However, this article was incorrectly released under the title Microsoft Dynamics GP “12″ Multi-tenancy Architecture .
Back at the Microsoft Dynamics GP Technical Conference 2011 in Fargo, ND and Microsoft Convergence 2011 Atlanta , my sidekick, David Musgrave thought it would be a good idea to introduce my hometown, San Andres Island , as part of our presentations and give all attendees to our sessions a free ticket to the island.
I received a lot of feedback from the community as a whole on the 3-part series of articles on Microsoft Dynamics GP “12″ Web Client Architecture and I was pleased to know that many of you are embracing the fact that there will be a Web client version of the product and are asking numerous questions about readiness. While these articles addressed the client portion of the solution, I really did not mention anything about changes in the database architecture and how these will impact the future deployment options. So, I have released a new architecture article on Microsoft Dynamics Community , this time addressing Microsoft Dynamics GP “12″ Named System Database Architecture .
If you have recently upgraded to Microsoft Dynamics GP 2010 R2 , a few days aback, a partner reported receiving the following errors when returning from Report Writer: Unhandled script exception: Illegal address for field ‘Not Found’ in script ‘Unregister_Triggers’. Script terminated. EXCEPTION_CLASS_SCRIPT_ADDRESSING SCRIPT_CMD_LOAD_ATSI7 Unhandled script exception: Illegal address for field ‘Not Found’ The error is followed closely by: Unhandled script exception: Object has no reference.
Cannot insert the value NULL into column ‘SEQNUMBR’, table dbo.IV10400, column does not allow nulls. UPDATE fails.
Today, one of my customers reported the below error message whenever they try to post any kind of inventory transactions: Microsoft SQL Native Client SQL Server Cannot insert the value NULL into column ‘SEQNUMBR’, table dbo.IV10400, column does not allow nulls. UPDATE fails