Sage 100

Has anyone run into an issue where a user-defined script won't fire on the post validate of one udf but it does on another? I have 2 PO detail udf's(length and width) and i have the same script firing on the column post-validate of each. It executes on the width UDF and not on the lenghth UDF. I added another udf called LEN just to see and it won't execute on it either. Any ideas?

Never had this problem. Only if there was an invalid statement that would not compile. I have had some tables that I thought should have triggered an event only to find out that they are ONLY modified by journal update therefore the events will never fire even though they can be setup. Of course this doesn't apply to PO Detail.

I've never had it happen either. It's a 4.40.0.6 install. They are PO Purchase Order Detail UDFs. I've simplified the script down to printing a message box. It executes fine on my UDF_Width field but I can't get it to fire off on a UDF_LENGTH field and I made another new UDF_LEN field and it won't fire off on that one either. I have the UDF's on the PO Entry lines grid.

Any chance the UDF names are similar to a field in the table already? I vaguely recall issues if the names were the same or similar.

I would try re-running customizer utilities. If that doesn't do it then I would force an error in the script and run Debug to see if the UDF's appear in the BO.

Jeff - I wondered..that's why I created a new one called Len(Although, I think i've actually used LENGTH successfully in the past) Dan - I'll try but It really doesn't seem like it's getting to the script to even cause the error in the first place.

Sometimes just adding - then deleting a new UDF forces a re-compile that can solve problems.

I meant that you would force an error on the UDF that worked and see if the other UDF's are present in the Dump.

Ok Dan, I'll give that a try and let you know what I find. Thanks.