Sage 100

Doclink gurus - Why do the Sage 100 panels have to be rebuilt by Doclink for a ""simple"" migration from v2016 STD to v2018 ADV (new server)? Seems like they have done the work once, why a complete rebuild?

Still puzzled here. From Doclink. **Yes, our Development needs to merge the screen customizations for the new Sage version and this is a billable activity as indicated in the Statement of Work (SOW** Why doesn't the migration of the v2016 panels transfer the Doclink links to v2018? On the surface, this seems like double dipping.

We've not yet moved a DocLink customer to v2018, yet it seems that they need to confirm that the screen customizations are still correct, fields are in remain in the right place, and don't run into any other customizations the customer may have on that screen. We do this as part of our upgrades, too, eventhough there may not be any action needed. If they have an importable file for their screen customizations, they could remove/overwrite any others that the customer has, which would be worse.

DocLink uses scripts (especially buttons), often with hard coded paths and SQL connection strings. My guess is the screen customizations are coming over during Migration but they are verifying the scripts and SQL connections still work and don't need adjustment. Also sometimes their buttons are buried under other controls after you run Customizer Panel Update utility. That's my theory but instead of charging it as separate billable activity, I would have included this in the Upgrade Cost they quoted you to go to 2018 or included it in the Annual Maintenance.

Here is the scoop. Doclink is wanting 16 hours to move the links to v2018. They requested panels from v2018 that were ""clean"" meaning after the install but before I migrated (which moved the panels doclink) panels. Off the top of my head, either they don't know how the panels migrate, they are sandbagging the client or something else. Guess it is time to ask them what is going on!

See my chat.