Automation Beyond

Testing and Test Automation for Software Quality Assurance. Above Requirements. Beyond Expectations. Methodologies and concepts. Framework Design. Programming and Scripting. Created by Albert Gareev.

«
»

MS Dynamics Great Plains: Built-in Macro System

Posted by Albert Gareev on 2009/11/12

Relocated:

http://automation-beyond.com/2009/11/12/ms-dynamics-great-plains-macros/

This entry was posted on 2009/11/12 at 08:32 and is filed under 2. External, Automation, MS Dynamics Great Plains. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

7 Responses to “MS Dynamics Great Plains: Built-in Macro System”

  1. Reference Page – GP/QTP Automation « Automation Beyond said

    2009/11/12 at 09:21

    [...] MS Dynamics Great Plains: Built-in Macro System   [...]

  2. GP/QTP Automation: cross-dictionary issue with sanScript « Automation Beyond said

    2009/11/12 at 09:23

    [...] However Dexterity Macros could be used as a workaround [...]

  3. GP/QTP Automation: Creating Dexterity Macro XML template « Automation Beyond said

    2009/12/07 at 09:08

    [...] One of the major limitations identified in Dexterity Macro System is totally hard-coded data with no functionalities to read them from any external source [...]

  4. Generating text file from XML template (QTP, VBScript) « Automation Beyond said

    2009/12/09 at 08:35

    [...] The current logic is oriented to executable text files generation, like Dexterity Macro [...]

  5. How to use loops in Dexterity Macro « Automation Beyond said

    2009/12/21 at 08:11

    [...] MS Dynamics Great Plains: Built-in Macro System [...]

  6. GP/QTP Automation: Execute Dexterity Macro « Automation Beyond said

    2009/12/23 at 08:13

    [...] One of the major limitations identified in Dexterity Macro System is totally hard-coded data with no functionalities to read them from any external source [...]

  7. GP/QTP Automation: Conclusion but not closure « Automation Beyond said

    2009/12/28 at 08:39

    [...] The issue was resolved by using Dexterity Macros to bypass GUI forms defined in third-party dictionaries and thus inaccessible through sanScript [...]

Comments are closed.

«
»