Distribution, Manufacturing, and Internet Modules

[zip]

MAS 200 4.40 PU5. S/O Entry line item Extended Description changes are not saving properly depending on the location of the Description field in the primary grid:

With the Description field moved to the S/O Entry primary grid, call up an existing S/O, click on the Description field data of a line item with an Extended Description to bring up the Item Text Maint window, make a change to the desc, click OK, click again on that Desc field data to bring up the Item Text Maint window, and notice the change is gone.

It seems like the only time this doesn’t happen when the Description field is in the primary grid is if that field is in the last position (farthest to the right) – or if the field is left in the secondary grid.

Have others seen this? Any other workaround besides putting it in the last position on the right, or leaving it in the secondary grid?

[roger77]

It's definately not saving it unless it's last in the grid.  almost like there's an invisible "ok" button that saves it once you enter out of the field.

for now, i have them 'entering' till the end of the line, not sure if they were typing in the ext desc and then clicking away from the line, but i have them hitting enter until it goes to the next line.

[roger77]

oh hey, it's me.   i lost my original login on here.

-ben

[skirmoochsage]

Brett: I'm not able to dupe a problem with the extended description field contents not being saved (although I do find a possible 'first time in' issue), but maybe I'm not following similar steps. I did find a 4.40.0.4 fix (PER 110352). If you are on 4.40 PU4 or newer and have this issue, can you report your issue to support so we can get it researched? Thank you.

[roger77]

I'll do a report from in front of it on monday.    Let ya's know. 

thanks.

[zip]

We're on PU5.  What is PER 110352?  Don't believe I can locate that in SSO.  Can you post it here, please.

[roger77]

You're on this one, Zip.   Call me tomorrow when you wanna connect in.

I still want to know when it actually writes the extended description.. I think i'm on to something saying they have to enter through the line the whole way to save it.  

I'll happily investigate this exchange for all the master developer toys, if anyone at Sage is listening..

[skirmoochsage]

Sorry Roger77, my system tracks by the bug report number, whereas Sage online uses the concept id.

In the Knowledgebase link, type in 526547 in the Quick Search/Enter Resolution ID field.

I'm sorry for any confusion and inconvenience.

[zip]

That does seem similiar but doesn't appear to be the exact issue.

[roger77]

re: 526547

nay, we're on 4.4.5.   close, but what actually happens is:

existing order.   these people USE extended descriptions like i've never seen at any mas users elsewhere.   11 out of 10 lines on an order have at least 4-5 lines of description. 

here's a short example:   DWG NO. A10810 REV C (STOP TUBE DETAILS FOR IT39 SET .XXX) 304SS TUBING, WELDED AND DRAWN, HARD TEMPER, .0460" ± .0005 OD x .0340" ± .0015" ID CUT AND DEBURRED TO .915" ± .005 LENGTH, PACKAGED IN PLASTIC VIAL

that's a short one.  last place i upgraded, i gave up on the extended and made 6 120 character line udfs, and that's working way better.   here, i can't do that.    

point being, they're very very specific.   very.    and those numbers are very crucial, and what happens is, they'll print out a sales order, see something off, and go back in to change it.      Sometimes, the changes don't save.   sometimes.    sometiems they do.    it's not consistant, it's not one person, one workstation, etc.   its happening to enough different people and workstations to make it so that it has to be a system problem, not a user or workstation.  i'm rambling a little, but it's crucial here, with their level of detail.