Customizer Import Refuses .M4X file from the same version (both are Sage 100 2022 7.10.2.0 32 & PR 2.23.0.0 32-Bit)?

Why would a Sage 100 2022 Customizer Utility import fail if it is used to copy from a ".M4X" file a P/R UDT, VI jobs, and event script to the same level (Both are Sage 100 Standard 7.10.2.0 and P/R 2.23.0.0) from which it was created?

Parents
  • 0

    Further isolation of this issue indicates that it is the UDT portion of the import that causes the Customizer Import Wizard message above. I have tried this in two separate 2022 PU2 systems and both had the latest P/R 2.23.0.0 version. The P/R UDT has only two fields. They key is a 14 character field plus a second 40 character field.

Reply
  • 0

    Further isolation of this issue indicates that it is the UDT portion of the import that causes the Customizer Import Wizard message above. I have tried this in two separate 2022 PU2 systems and both had the latest P/R 2.23.0.0 version. The P/R UDT has only two fields. They key is a 14 character field plus a second 40 character field.

Children