Sage 100

SetValue on the ItemCodeDesc "should" be all that is needed. (I know in VI it is all automatic, but am not 100% sure about scripting).

I'd expect something like a -1 retVal and warning text (about too many characters), but Sage programming "should" translate the longer item description value into the extended record automatically.

Kevin, I would expect the same, it doesn't.....I found this old entry that included you in Sage City

https://communityhub.sage.com/us/sage100/f/business-object-interface/159284/setvalue-for-itemcodedesc-creating-extended-descriptions/450744

But that doesn't seem to be working on the Sage 100 2023 Premium they are on....

SetValue on the ItemCodeDesc "should" be all that is needed. (I know in VI it is all automatic, but am not 100% sure about scripting).

I'd expect something like a -1 retVal and warning text (about too many characters), but Sage programming "should" translate the longer item description value into the extended record automatically.

Kevin, I would expect the same, it doesn't.....I found this old entry that included you in Sage City

https://communityhub.sage.com/us/sage100/f/business-object-interface/159284/setvalue-for-itemcodedesc-creating-extended-descriptions/450744

But that doesn't seem to be working on the Sage 100 2023 Premium they are on....

SetValue on the ItemCodeDesc "should" be all that is needed. (I know in VI it is all automatic, but am not 100% sure about scripting).

I'd expect something like a -1 retVal and warning text (about too many characters), but Sage programming "should" translate the longer item description value into the extended record automatically.

Kevin,

Thanks for feedback!  It doesn't appear to be working though on a pre-write event.  Here is what happens

Item initially

make a change to a field on the item, click "Accept" and this comes up

Click "OK"

This comes up:

Click "OK" and the record act's like it's saved.

Go back to the item record and notice it didn't actually create/update the extended description

Do you think I would need to do a hidden button over accept and call my own code then the accept button?  I see yours was firing from a button.

Kevin, I would expect the same, it doesn't.....I found this old entry that included you in Sage City

https://communityhub.sage.com/us/sage100/f/business-object-interface/159284/setvalue-for-itemcodedesc-creating-extended-descriptions/450744

But that doesn't seem to be working on the Sage 100 2023 Premium they are on....

SetValue on the ItemCodeDesc "should" be all that is needed. (I know in VI it is all automatic, but am not 100% sure about scripting).

I'd expect something like a -1 retVal and warning text (about too many characters), but Sage programming "should" translate the longer item description value into the extended record automatically.

From what I understand, InvokeChange mimics user data entry... and the nuance of how that might work on a pre-write event is not something I can say much about. 

My general rule: try different things until you find something that works!  Changing to an Accept+ button is certainly worth a try. 

(I like to name enhanced Sage buttons with a "+" to have a visual indication they are running the customized button).

Kevin,

Thanks for feedback!  It doesn't appear to be working though on a pre-write event.  Here is what happens

Item initially

make a change to a field on the item, click "Accept" and this comes up

Click "OK"

This comes up:

Click "OK" and the record act's like it's saved.

Go back to the item record and notice it didn't actually create/update the extended description

Do you think I would need to do a hidden button over accept and call my own code then the accept button?  I see yours was firing from a button.

Kevin, I would expect the same, it doesn't.....I found this old entry that included you in Sage City

https://communityhub.sage.com/us/sage100/f/business-object-interface/159284/setvalue-for-itemcodedesc-creating-extended-descriptions/450744

But that doesn't seem to be working on the Sage 100 2023 Premium they are on....

SetValue on the ItemCodeDesc "should" be all that is needed. (I know in VI it is all automatic, but am not 100% sure about scripting).

I'd expect something like a -1 retVal and warning text (about too many characters), but Sage programming "should" translate the longer item description value into the extended record automatically.