Splitting globaldimension 1 to companies

SanderK

I have a question about creating companies for the global dimension 1 code (Department) in a customer database.

The global dimension 1 (Department) are the different companies of this customer.

Instead of different companies in the database the customer uses Global dimension 1 code (Department) as filter on every form.

Due to the high maintenance regarding upgrade's the customer wants to split the department's to different companies.

What is the best way to do this?

For example : Is it possible to temporalily change de datapercompany to dataperglobaldimension1 make backup's and import these backup's in the different companies?

kine

I think that not easy way exists. For me it seems like you need new start for both companies, export old data, import them back into new companies, but you will not have full details, becouse it seems that some data cannot be transfered without problems... (for example data without Dimension 1 etc.)

DenSter

A filter like that can be merged into a new version by a junior level programmer in half a day. You only do an upgrade once every so many years, I don't see how that could be looked at as 'high maintenance'.

What you are talking about here is a full scale project to split one database into multiple companies, and you're gong to have to think about consolidation and synchronization of various shared data.

I would reconsider going in this direction.

BTW I used to live right around the corner from you Sander, in Krimpen

SanderK

There is a lot more custimization then a filter on a form, i only used this as a example.

Think of every new solution from Navision/Solution Partner it has to be altered to work in the database. For example E-VAT, the calculation of the inventory posting.

I also used to live in Krimpen

DenSter

Right, and an upgrade is more than just merging a form filter, I understand. The point I am trying to make though is that merging your customization into a new set of objects going into that database is a relatively small job compared to splitting up a company. I have done extensive merging of objects into many databases and I got to a point where I can have an entire database with many add-ons technically upgraded (i.e. get the objects merged and fully compiled) in a matter of a couple of days.

I'm not saying it's a bad thing to split the companies, I just don't think that you're doing it for the right reasons, if the upgrades are the only ones.

I remember riding my bike over the Algera bridge on my way to school, I must have scaled that thing 2 million times 8-[

Captain_DX4

I think what would be best done (in my limited accounting knowledge) is to use the existing company as a consolidation company and perform fresh setups on several new companies to correspond to the different departments.

If you start splitting apart your ledgers, you'll either have a bunch of gaps in numbering sequences (bad from an audit standpoint), or a bunch of work in renumbering the entries with no guarantees about making the navigate features in Navision work at all again (for the older records). But if you look at the migration as several smaller tasks of exporting and importing into fresh, new companies with no expectation to bring over the history (just beginning balances), then you can effectively get to where you need to be with less headache, in my humble opinion. Then have your customer look into training on setting up the consolidation company if they desire.