Sage 100

Working on a Sage 100 v4.3 Standard PU 23 to Sage 100 ERP 2014 PU 5 Have significant UDF fields in the item master Most UDF data migrates and converts just fine There's a decent chunk that is not converting and I have just blank UDF data in the 2014 system. Have not seen this before where a portion of the UDF migrate and a portion is apparently just dropped. Anyone have thoughts? I rebuilt keys on 4.3 and rebuild Custom Office on 4.3. No unusual looking errors.

In the 2014 MAS, have you tried opening the UDF fields in Custom Office and hitting the update button. This may straighten out any data dictionary problems you may have? I would try that first

I tried it however when I look at CI_Item in 2014 and drill into a problem item the values are empty so I presume I'd have to reconvert data to know if this works. Unfortunately it's probably 4 - 6 hours converting.

I've not seen that one either, Wayne. That's at least a fairly easy issue to get around though, if need be. Export all the UDFs from 4.3 and import them into the new installation.

Thanks - customer is going to ask who, what, where, when, why. Opening case with Sage to say that I did. Expectations low.

Can you see the values in 2014 CI_Item using DFDM?

They are not present in 2014 CI_Item. I can see them in 4.3 CI_Item.

I had this twice on similar upgrades (4.3-2013, etc). Never opened a case because I needed it fixed before Sage would be able to do anything, and just did what Brett suggested - exported from 4.3 and imported into newer version. Only bad thing at one location is that they didn't own VI so had to swap the file back and forth to my system...

Thanks - I could swear someone ran into this and was thinking it was you. Any theories?

One weird thing -- still would have to check -- the items which did NOT migrate UDF have the UserUpdatedKey$ as blank. The UDF that DO migrate have a value in the UserUpdatedKey$

I had no theories because I didn't have time to think about it. First client to have this happen suffered through an early adoption 4.10 upgrade, where I first learned that when you reconvert a company, it wipes out everything in that company's Reports folder. (Labels, lots and lots of LABELS.) Needless to say, just had to get this issue fixed ASAP this time so they'd never know it happened. So this is the UserUpdatedKey in the CI_Item record? And is it ALL UDFS? Seems like mine was only SOME of the UDFs didn't migrate, for all items.

On mine this is only some UDFs as well. When I DFDM CI_Item on v4.3 I can see that the items which did not convert all are missing (null) the UserUpdatedKey in CI_Item. This is a company where they have done a lot of VI so it's possible at some point someone hosed an import and somehow created these records (17,226 out of 58,000) without a user key? Trying to think of the best way to put something in the userupdatekey so I can see if that fixes the issue Unfortunately there are several poor migration practices with Sage -- including the inventory balancing utilities which read live data and make changes during a test upgrade unless you work from a separate copy of the data. The more I see the more I understand why Sage is in distress.

Weird, but definitely a possibility. Could try exporting them out and importing in just the item code again and see if that updates that field.

Working on that now

I'm getting an error ""Inventory Items Must Be Changed Via Inventory Until 4.3"" - I know I've seen this but can't remember the cure. I'm trying to VI in just the Item number to CI_Item

Looks like up to 4.3 have to import to IM.ITEM

Tried exporting out the entire CI_Item and reimporting to IM.ITEM. This appeared to work but unfortunately the UserUpdatedKey$ did NOT change although the date and time updated did??

Even stranger - manually going to IM Maintenance and making a change in a record (where the userupdatedkey$ is blank) and saving does NOT seems to add a record to the user updated key field. VI didn't add a record to userupdatedkey$ and neither did making a manual change -- yet the date/time does get updated.

Yikes. SO the only way to test would be to stuff a value in there via DFDM on a couple of records and reconvert.... ACK.

And even stranger - comparing 4.3 pre-conversion to 2014 post -- there are four UDF in 2014 which have been converted. The rest are blank. At this point I'm recommending that we do the same as what you did - just VI in the UDF fields. Strange. Sad.

Pulled a case with Sage after 1:05 on hold. Not unsurprisingly they had never heard of this before.

See, that's the thing. Half the time no one wants to take the time to call them, just to have them diddle around, so it could be happening a BUNCH and Sage doesn't know. It's like the missing tier field - at least of us on 90 Minds have reports of this happening, but when I reported it to Sage, they were clueless.

And clients wonder why these upgrades cost as much as they do.

This customer has about 10 GB of data. Naturally Sage wanted me to zip it up and send it to them. The last time I sent data I never heard back from Sage until I inquired 3x about their progress. Unless I'm on a mission critical / system down type error I am not going to send Sage any more data.