I was actually thinking about a similiar what-if scenario like this the other day, but it was more along the lines of if the data was still there but if another supporting resource that maps these fields didn't get updated.

For example, UDFs would likely also need to be transferred to resources such as .\MAS90\providex.dde

Or ProvideX.ddf also has some references to UDF related entries.

So essentially where I am getting to is what if you were to pull up the new .M4T table in DFDM to verify if those UDFs still show up there with it's data intact. Perhaps the UDFs did transfer they just aren't being recognized by Custom Office due to a bug that might be easier to fix with a patch.

If they did exist, then maybe re-adding the UDFs in custom office (certainly after a backup and with the same attributes, i.e. data type, length, etc) would recreate the references to them and with them already existing in the table it may (hopefully) not replace the data. I obviously don't have the answer but I would certainly check the new table in DFDM first to see if they show up there by some miracle.

I don't know about Scanco's version of PM but we were running Sage 2016 with the work order module when we upgraded to Sage 2022 with Production Management.

The 2016 environment previously used Scanco/ACS multibin and had since switched to Scanforce/DSD multibin - so the Scanco UDFs along with user-created UDFs were present in the WO tables.

When upgrading to Sage 2022 all of the UDFs were converted along with their data - including the now defunct Scanco UDFs 

This client is Premium and the new PM SQL tables do not have the UDF's.

Kevin,

We were able to reproduce this issue with the JT UDFs not converting to PM on premium.  Not sure what is happening, as it seems to be something in the Premium conversion. Standard conversion works fine. We have created a defect and are looking into it. 

Thanks,
Kent

Thanks for confirming Kent. 

This upgrade went Live yesterday, and I dealt with things manually over the weekend (UDFs recreated, then SQL scripts to copy in the missing data). 

Any fix will be important for future Premium upgrades with JT to PM conversion.