"If this is an upgrade, consider upgrading to just Sage 100 2020 for now, rather than Sage 100 2020 with Product Update 1"
That is some world class advice right there. 11 pages of fixes and the advice is to upgrade without it?
@Jeff Schwenk your case referenced above didn't even have any lotserialhistory records?
------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960
https://www.firstmatellc.com/------------------------------
Original Message:
Sent: 10-13-2020 20:39
From: Wayne Schulz
Subject: v2020 PU1
Aside from bug fixes wasn't this the main new feature in PU1?
- If this is an upgrade, consider upgrading to just Sage 100 2020 for now, rather than Sage 100 2020 with Product Update 1
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------
Original Message:
Sent: 10-13-2020 17:19
From: Brett Zimmerman
Subject: v2020 PU1
Just noticed the following on the PU1 page for v2020:
<content>
</content>
Data Conversion hangs on IM_LotSerialTransactionHistory in Sage 100 2020 Product Update 1 (2020.1)
|
<content>
- Data Conversion hangs (freezes) on IM_LotSerialTransactionHistory in Sage 100 2020 Product Update 1 (2020.1)
</content>
| Backup Warning |
|
Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst.
|
<content>
Sage Engineering is currently reseaching this issue
Possible Workaround:
- Let conversion run until complete.
- Caution: This may take hours. For those with several hundreds of thousands of records in the table, this may take a day or more.
- If this is an upgrade, consider upgrading to just Sage 100 2020 for now, rather than Sage 100 2020 with Product Update 1
</content>
<content>112421</content>
ID:107126Last modified:10-9-2020
------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
Original Message:
Sent: 10-02-2020 18:57
From: Jeff Schwenk
Subject: v2020 PU1
Hmmm, thought it might have to do with having 15 years of inventory transaction but it was all fifo or standard cost. My conversion took a long time,. Fairly certain it was the PU1 serial number "enhancment"....
------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
Original Message:
Sent: 10-02-2020 11:57
From: Shannon Stanley
Subject: v2020 PU1
Had the same issue with a client coming off v2017 SP6 and the conversion stopped and never finished. None of the companies on this account have made it past this point in the conversion process. Opened a ticket with Sage a day ago and was told today that they have found the issue. They believe its related to service pack 1 and said hopefully engineering will have a solution by next week.
------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
704-839-6697
Original Message:
Sent: 10-01-2020 14:44
From: Wayne Schulz
Subject: v2020 PU1
Could this be related to the new lot/serial traceability feature which I believe was added in PU 1?
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990