Open Forum

Like what you see? Discover the benefits of the GPUG Community. Learn More

Extending Capabilities of Report Writer using Dexterity

  • 1.  Extending Capabilities of Report Writer using Dexterity

    TOP CONTRIBUTOR
    Posted 7 days ago

    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

    Dynamics GP Tips and Traps For Users and Developers remove preview
    Extending Dynamics GP Report Writer Capabilities with rw_Dexterity functions
    You can greatly extend the capabilities of the GP Report Writer with the use of the special rw_TRIGGER functions that enable you to access data from any third party table using Dexterity, or any data source using .NET with Dexterity if you wish.
    View this on Dynamics GP Tips and Traps For Users and Developers >



    ------------------------------
    Bruce Strom
    Programmer Analyst
    Associated Grocers of Florida / Supervalu
    Sunrise FL
    ------------------------------


  • 2.  RE: Extending Capabilities of Report Writer using Dexterity

    GPUG ALL STAR
    Posted 7 days ago

    @Bruce Strom

    GP Power Tools uses triggers on these functions to provide the ability to create custom RW functions in your system without needing to create your own Dexterity dictionary.

    You just add your code into the template scripts provided in the Runtime Execute Setup window. No need to create or deploy a chunk, no need to restart GP.

    Regards

    David

    ------------------------------
    David Musgrave MVP, GPUG All-Star

    Managing Director
    Winthrop Development Consultants

    Perth, Western Australia

    http://www.winthropdc.com
    ------------------------------



  • 3.  RE: Extending Capabilities of Report Writer using Dexterity

    SILVER CONTRIBUTOR
    Posted 6 days ago
    Edited by Anthony Merriwether 6 days ago

    Disadvantages(Problems) of Triggers

    • It is easy to view table relationships , constraints, indexes, stored procedure in database but triggers are difficult to view.
    • Triggers execute invisible to client-applications. They are not visible or can be traced in debugging code.
    • It is hard to follow their logic as they can be fired before or after the database insert/update happens.
    • It is easy to forget about triggers and if there is no documentation it will be difficult to figure out for new developers for their existence.
    • Depending on the type of trigger used and the particular field used to trigger, it/they may run every time particular database fields are updated.
    • There is additional system and network overhead associated with using triggers and can cause your system to run slower.
    • Triggers will require elevated database access roles to employ and will generally require the assistance of an already overburdened IT staff.
     I am not a big fan of triggers and I use them only as a last resort...

    ------------------------------
    Anthony Merriwether
    ETL Source LLC
    www.etlsource.com
    amerriwether@etlsource.com
    ------------------------------



  • 4.  RE: Extending Capabilities of Report Writer using Dexterity

    TOP CONTRIBUTOR
    Posted 11 hours ago

    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.



    ------------------------------
    Bruce Strom
    Programmer Analyst
    Associated Grocers of Florida / Supervalu
    Sunrise FL
    ------------------------------