Data Repair in Microsoft Dynamics GP Part II
This video is the second in the series of GP data corruption and fixes Here we review two scenarios. The first one is when Dexterity customization deals with so-called Open or Historical tables (in the case of Receivable management they will have naming conventions as following: RM2XXXX and RM3XXXX) Why customizations? The answer is simple – they are likely unique for your specific requirements and chances are high that developer didn’t have budget to do decent Quality Assurance Second scenario is batch posting or computer checks selection and building in Payable Management or Payroll. These processes take from several seconds to several minutes and if you have power outage and computer crush then depending on where the process was interrupted you will have to conduct your repair work on work or open tables (or the combination of two and in the case of PM or SOP also the historical ones) Andrew Karasev 331-330-6879 akarasev1964@gmail.com
This video is the second in the series of GP data corruption and fixes Here we review two scenarios. The first one is when Dexterity customization deals with so-called Open or Historical tables (in the case of Receivable management they will have naming conventions as following: RM2XXXX and RM3XXXX) Why customizations? The answer is simple – they are likely unique for your specific requirements and chances are high that developer didn’t have budget to do decent Quality Assurance Second scenario is batch posting or computer checks selection and building in Payable Management or Payroll. These processes take from several seconds to several minutes and if you have power outage and computer crush then depending on where the process was interrupted you will have to conduct your repair work on work or open tables (or the combination of two and in the case of PM or SOP also the historical ones) Andrew Karasev 331-330-6879 akarasev1964@gmail.com