Triggers are designed to work identically whether you are using your development dictionary (in test mode), or operating in a multidictionary environment (at runtime). However, you should test your application’s triggers in a multidictionary environment as much as possible, because this environment most closely matches your customers’ environment.
Triggers will allow you to change core application functionality. For example, when using a focus trigger with a field, the reject script statement will prohibit the change script for that field from running.
When testing and debugging your application, it’s important that you account for all situations where you may be affecting Microsoft Dynamics GP functionality, such as in the previous example. During the testing process, you can enable and disable your application’s triggers appropriately to locate the source of application errors.