Normally you can resolve majority of issues by login CustomerSource and searching knowledge base. If you are reading this publication then probably you do not have annual maintenance contract and you access in blocked.
As general observation we would like to say that older versions were working in Dexterity encapsulation and the number of known issues was related to bugs in Dynamics.dic. Integration with MS Office stack, Web Service, eConnect and Service pack application method introduced ‘technology related’ issues. Here we are talking about versions 9.0, 10.0 and 2010. We will try to sort cases by their ‘popularity’:
1. Interrupted batch posting. It typically happens when you initiate large batch posting and switch your computer to another activity (reading email, surfing internet, etc.) or if your computer shuts down due power outage. This issue was so popular that Microsoft introduced Batch Recovery form (Tools -> Routines -> Batch Recovery). Please read Status first and open help for the form. Status is important. For example if it is ‘Transaction Error – Edit Required’ then you can enable batch for posting but it will fail again with the same status. Instead enable batch, open it and print Batch Edit List. Chances are high that in some documents distribution GL accounts are missing. Open these documents and add missing distribution accounts. However we realized that in certain complex situations you need SQL data repair especially in AP Computer Checks and Payroll Checks. In older versions (we believe 6.0 and earlier) you have to fix batch record in table SY00500 (reset ‘batch status’ and ‘market for posting’ fields to zero)
2. ‘This user is already logged’ problem. This problem happens when you do not log off from Dynamics and later on computer is shut down or maybe somebody else is using your ID. In new releases simply go ahead and delete it when suggested (assuming that your boss is not currently logged under your ID…). In earlier versions in the case of eEnteprise or GP in SQL use the following statement in Query Analyzer: delete activity where userid=’Mark’ (please use real ID in your statement). Execute it against Dynamics database. If you are on Pervasive SQL 2000 or Btrieve then ask all the users log off and delete Activity.* files in Dynamics\System directory on the server
3. Strange Error (something like unknown error – would you like to report to Microsoft?) when you are trying to print modified report (ReportWriter). This is likely due to Reports.dic corruption on the file level. In our opinion it might happen when you have large number of modified reports and one of the users is modifying them while others are printing these reports. What seems to work is log users off, renaming Reports.dic (please be sure to review Dynamics.set file to learn where dictionary is located) and then go to Report Writer and import all reports from the renamed dictionary
4. Great Plains DOS issues. Here they are often related to incorrect Pervasive SQL 2000 settings. By the way GPA is still supportable as Microsoft compiled all known issues in Excel worksheet
5. For additional information, please feel free to call us 1-866-528-0577 or 1-630-961-5918 (this number works for international customers) or email us help@albaspectrum.com We serve you USA/Canada nationwide via remote support (web sessions and phone/Skype conferences). Local service is available in Western Michigan, Chicagoland, Southern California (LA, Orange County and San Diego) and Houston area of the state of Texas
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
