Why Choose Dexterity for customization/modifications.

Once upon a time More than one upon a time, client insist to not have customization in dexterity because they thinks it will cause issues, unknown errors, system crash and will require many more hours of coding and testing. In this case it was modifications of gp default reports like SOP and POP blank papers, short and long form etc, modification was to get some information from 3rd party/custom tables and print them on report,  so instead of suggestion to have this modification in dexterity they went for report writer modifications along with vba coding just to avoid the dexterity/chunk deployment. Years passed.

Then the issue came with some of their users using GP web client so vba was not working, workaround was to print reports from the regular GP installation and all was good.Again years passed.

Then client moved to windows server 2019 and all the sudden vba code stopped working because it is not supported by the OS. I also saw similar issue related questions on GP forum and people were asking for alternatives. Alternatives like moving vba customization to .Net or VSTools. Moving customization to VSTools is something one can go for if the customization is related to GP windows, but for reports modification looking for other option like designing custom reports in Crystal or SSRS is difficult to understand,  it has disadvantages of it’s own.

• • You have to design a complete new report.
  • You have to work for each format separately.
  • If GP default report is updating document status on printing then it means we will be missing those updates in relevant GP table.
  • You will miss wide variety of print options available on print options window.
  •  You will miss the beauty of report writer reports.
  • You need custom window for report selection and the lookups their will be not as friendly as gp lookups

But as dexterity sound more confusing to many people, People usually go for custom .Net utilities then dexterity.

sadly. : (