All related posts: Reference Page – GP/QTP Automation 

The problem 

Those who tried sanScript code examples on their windows/objects probably noticed that Great Plains refuses to execute some instructions referring to certain objects even if they were successfully mapped with Dexterity GUI Mapping Script or with GUI Capture Script.

And while  highlighting  window controls you may see that some were “omitted”.

The reason is that those GUI objects do not belong to the base product package or dictionary as it is named (filename: Dynamics.dic).

Those who are interested in researching the problem from the application development side might find useful the following articles. 

Understanding Cross Dictionary Dexterity Development 

Cross Dictionary Dexterity Development 

There is no solution for the cross-dictionary scripting issue but modification of source code of the application’s dictionaries and this way is not really applicable for the functional test automation.

However Dexterity Macros could be used as a workaround.

See detailed examples in the next blog posts.