Sage 100

Upgraded from 2013 to 2015 today. Sales order ""Quick Print"" returns ""Data is not Selected for Printing"". Sales Orders print fine from the Sales Order Printing menu option. Quick print works OK in ABC company.

I had a customer get this message after their upgrade. They had not installed the product update before migrating and converting their data. Could this be your situation?

I installed the product update before the migration and data conversion. How did your client fix this? New orders don't quick print either. Even if the PU was installed later one would expect new orders to quick print.

Yes, you would expect the update to correct the issue regardless of when it was installed, but that didn't happen. Try making a copy company and see if quick print works. They ended up making a copy company and then copying it back. But if it works in the copy, I think I would re-migrate and convert.

I will try copying to another company tomorrow. Thanks for the advice.

Issue was noted during VIP and was supposed and the fix was included in PU1. See attached. I would suggested contacting tech support. If it wasn't included in the PU1, then it needs to be fixed ASAP. In any event, based on the resolution posted for the VIP's, your file needs to be repaired by Sage.

I spent 30 minutes with Sage support yesterday and they are ""researching"". I copied CCS company to CC2 company this morning and the issue magically disappears in CC2. the only issue is that credit cards, forms etc have to be manually set up in the new company. At least there is a work around. Thanks @JaneCavanaugh and @JeffSchwenk

Just sent SY_ReportOption.m4t to Sage for repairs.

If you copy CC2 back to CCS, does that fix the problem?

It might but they are working fine now on CC2 so may try later just to see.

I'm glad CC2 worked. Please let me know how the Sage fix goes. I wonder if their fix is something we can do ourselves. It looks like the fix in PU1 doesn't always work.

We can probably fix ourselves but I don't have time to compare the records to figure it out. Let them do it and then I will look and see what they changed. I will keep you posted when they get back to me.

Curious - were you able to see what Sage did to fix the issue?

No I wasn't. Linda Rabe of Sage sent me a patch - Sage1002015VIPPATCH_B It is a program you run that fixes the issue. So I am not sure what it fixes just know it works now.

@DougHiggs - Can you find out? This is a crucial issue. We need to know if the original patch included in PU1 was a stinker or that there is another issue...

My understanding is that PU1 will prevent the issue if installed prior to running the parallel migration. Patch B will fix the issue ""after the fact"" if the migration was performed prior to installing PU1.

I've added the patch to the 90 Minds DropBox, under 90 Minds Disks\Sage100 ERP 2015. Thanks @DougHiggs.