This blog linked is posted in the General Forum so users can be aware of what is possible, so you know what you can request from your consultant.
This shows how to use Dexterity to extend the capabilities of the Report Writer.You may be able to do the same using GP Power Tools, we will let @David Musgrave respond.We should thank David Musgrave for lobbying to include these functions in the Report Writer when he was working for Microsoft. (What were they thinking when they decided he should become an ex-employee?)In a prior blog we showed how you can add selected fields to the GP Inquiry screens using Dexterity, in this blog we will show how to add these same fields to the Inquiry Report Writer report.These two blogs have additional links to other useful blogs.Extending Dynamics GP Report Writer Capabilities with rw_Dexterity functions
Disadvantages(Problems) of Triggers
Your list of disadvantages of triggers are applicable to SQL triggers.
They do not apply to Dexterity triggers. Triggers are an integral part of Dexterity.You can view dexterity trigger code when debugging your code. Trigger code is just as easy to view as any other dexterity code. They are documented just as easily as an other part of code.Dexterity triggers do not require any elevation of database access, and Dexterity triggers can trigger off non-database events. They do not require additional overhead.
If you've found this thread useful, dive deeper into User Group community content by role