Handle common data between companies in one DB

S0918423470S0918423470 Member Posts: 159
Hello all,

I have a question need to help from all of you.
We have one DB ( NAV 5.0 Native DB) , we have some companies based on its own business processes.One is mother company and the others are daughter company. All of companies have "common" customer, vendor, Item.

Is there a possibility to use a common table (incl. communication info) with all customers for the different companies in one database? The same for Vendor and Item?

Thanks.

Answers

  • ebsoftebsoft Member Posts: 81
    Hello all,
    Is there a possibility to use a common table (incl. communication info) with all customers for the different companies in one database? The same for Vendor and Item?

    Thanks.

    You should create new tables (DataPerCompany=No), and insert records in those tables whenever you insert/modify/delete a record in each database.
    A problem could happen if you use the same Nos.
    You should use different nos for every company.

    Hope it can be useful.

    Federico
    Regards,
    Federico

    MBS Specialist since NAV 2.0
    My experiences on Linkedin
  • matttraxmatttrax Member Posts: 2,309
    Although data per company can be used it is not recommended because it is hardly ever setup correctly. For example, say you are storing customers across multiple companies and change the salesperson on it, or the default dimensions. If you have not also shared these tables across all companies you now have inconsistent data. The salesperson on the customer could be MATT, but that salesperson may not exist in certain companies.

    You can write code on the Insert / Modify / Delete triggers for the records you want to share without much effort.
  • S0918423470S0918423470 Member Posts: 159
    @ebsoft : thank for your reply, until you showed me about the DataPerCompany , i have not yet known about this properties. I will consider about this solution. Make some test cases.
    Before i posted my question in mibuso , i already had a solution like the way of Matt. I think using code to control data is good way, there is not much risk.
    With customer, when i created a new customer, i will do action (press button "Copy data" ), we can show many options to choose destination company ( specified company or all company). With the common data, i also have the way to control it how many company they were copied to support for modified or delete action.

    @ Matt : Is my solution good? I have some your books. Nice to discuss with you. :o
  • matttraxmatttrax Member Posts: 2,309
    It sounds ok to me. You have to worry about whether or not people remember to copy it or not. I've usually just done it automatically. It's not like DataPerCompany doesn't work, you just have to make sure you hit all the right tables, and that can be a problem.
  • S0918423470S0918423470 Member Posts: 159
    @matt : DataPerCompany is just used to have reference information between companies. If we want to use them to join business process ( SO,PO..) it's impossible because you must change many codes and it make high risk.
    The best solution is using code, maybe let it do automatically or do action.

    Anyway thanks all of you.
Sign In or Register to comment.