Here is another Quick Tip article. This time I wanted to discuss the best practices for making conditional triggers in Dexterity.
There are times where we might want to have a trigger which only runs under certain circumstances. There are a number of methods of handling these situations. This post will explain the various methods and when they should be used.
Some examples of when a conditional trigger might be used are:
So, now we have a number of reasons why we might need to make triggers conditional, what are the methods to create conditional triggers?
The four methods for creating conditional triggers are listed below:
In summary, the enabling and disabling of individual triggers method and the conditionally aborting method are the best methods to use. Dynamic or on-the-fly registration has its place, but enabling and disabling a product at a time is not recommended.
That's all for now.
Posting from Mark Polino at DynamicAccounting.net
i wana use trigger on condition debtor id =ADAMPARK0001 then save records otherwise dont save..
A trigger before the Save Record field change script with a reject script command should do the trick.
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.