x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 105 subscribers
  • Views 746 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Kevin M

Why am I forced to convert test company data after an upgrade?

SOLVED
Posted By

Note: this is more of a "why" question, not related to this thread (which was an enhancement conversion bug).

When upgrading a customer system (currently v2020 Premium to v2022.2 Premium), we bring along test company codes so user permissions (to their correct test company) are retained.  After the upgrade, I converted all the Live company data, which took HOURS to process, and skipped converting the test company data... planning to just refresh them with fresh copies of the converted Live data.

However, I am blocked from refreshing test company data without converting.

Why?  This seems like a complete waste of time, since I am about to wipe out everything in the test company codes.  Yes, I could remove a bunch of modules and decrease the processing time, but I have about a dozen test companies to go through, and the GL module (mandatory) is often the biggest data set... not to mention rushing through a series of module removals is not something I want to do routinely.

Obviously this error (checking conversion status before copying) was purposefully programmed for a reason.  I'm just curious what that reason is.

(BTW, I really like the company type filters on the bulk conversions... a big help for sure.)

  • 0

    Seems like you did this in the wrong order and are just annoyed.You aren't even looking for answer.That's a parallel migration, why the additional company? I did that same Premium upgrade last year.Yeah,major PITA.. Just delete it and remove it from SY_Company(?). Drop the test company database

  • 0

    I feel your pain, and also wish it would just "warn you" and give an option to carry on.  For companies that have specific test roles for specific users, dropping the test company and having to create from scratch is bothersome.  

  • 0 in reply to StefanouM

    Indeed.  I generally like to get everything done at the same time, so users can use the test companies on day 1 if they want to play with any of the new features... but when it's after 1am, I'm not waiting for the test companies to convert then copy, so I just do it later.

  • 0 in reply to pmaldonato

    I've done this many times and know I am doing things correctly.

    Deleting and re-creating the company codes would lose the user permissions to their specific test company.  Those are stored by CompanyKey, not the three letter company code.  Doing the conversion then copy is a fraction of the effort involved in replacing the permissions (for dozens of users, to about a dozen test companies), so your suggestion is not helpful.

  • +1 in reply to Kevin M
    verified answer

    FYI, I've exchanged emails with Sage, and their reasoning is that you can Copy individual modules, causing problems if the starting data doesn't have the new table / column structure... which makes perfect sense.

    My own thought (after posting) is that, for a migration from Standard / Advanced, the initial company conversion is what creates the MAS_### database in SQL, so checking for company conversion status will prevent issues with that scenario too.

    A couple thoughts came out of the email exchange, and I'll post an Idea with details when I have time to think it through properly.  When done I will post a link here so anyone interested can vote.

*Community Hub is the new name for Sage City