OE - CreditMemo, Apply to >remove default to 0 3

[leishad]

In OE when a user creates a Credit Memo I need to force them to enter an invoice#(would settle for any non-zero number) in the apply to field. I went into the screen designer and selected to make it required but this field automatically defaults to 0 if nothing is entered so that negates the required status for me. I checked within screen designer and the default value is not set to '0' there.

Any ideas?

 

[dgillz]

use Flexibility to force the entry of a value other than zero.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

 

[leishad]

Ahhhhh...I can't tell you the times that I wished we had Flexibility .....

 

[kscheeler]

If you don't plan on getting Flex anytime soon, you could use a SQL trigger that sets the apply to number field equal to the order number (that way it will be unique and not 0) for all credit memos that a user doesn't fill one in for.

It can be done on insert and is totally behind the scenes.

Obviously, test it to make sure it works the way you want it to.


Kevin Scheeler

 

[abaldwin]

If you decide to use a trigger you should test to insure that the records being updated do not equal 0 so that if a user enters a valid entry you do not overwrite it.

With your statement about Flex I would suggest you purchase Flex. Very small investment for a tool that you can do so much with.



Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[leishad]

Thank-you, I hadn't worked with triggers before and had just started reading about them....so it is good to know that my impression of their usefullness was correct --- now on to learn implemetation.

Thanks again

 

[abaldwin]

Leishad - you are correct in your statemnet of the usefullness and power of triggers. As much as we like to use them by themselves or in conjuction with Flex I would like to take a sanity check and remind you that you should be VERY carefull with their implementation and extensive testing before going live. You do not want to implement a trigger that will mess up the business logic and rules that you have in Macola.

Even with Flex itis important to understand the field, business rules, and proceedures so as not to incurr the wrath of messed up data a month after you implement something.

This is not to say not to do it, just a word of caution about testing and implementation of 3rd party tools to affect your ERP Data.



Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[leishad]

Thank-you --- proceeding with caution....