Customers, Items etc for all Companys in one Database

Campy

Hello,

we have Navision 2009 with 3 Companys.
Now all Companys should have Access to the Customers, Items etc.

Is there any possibility??

Best Regards

rnunes

Campy wrote:

Hello,

we have Navision 2009 with 3 Companys.
Now all Companys should have Access to the Customers, Items etc.

Is there any possibility??

Best Regards

Do you want the data to be shared to all companies? If so you have a property on the table (DataPerCompany) and you should put that to no.

Best regards,
Ricardo

Alex_Chow

Becareful about sharing the Item table. Read this blog post before sharing the Item.

http://dynamicsuser.net/blogs/alexchow/ ... n-5-0.aspx

DenSter

rnunes wrote:

Do you want the data to be shared to all companies? If so you have a property on the table (DataPerCompany) and you should put that to no.

For standard master tables this is such bad advice I'm not even going to address it.

Search around for this topic, in addition to the blog that Alex linked to. There are a LOT of topics about this subject. Personally I strongly disgree with setting any standard master tables to global tables, and would go an entirely different direction.

Savatage

Question - if all companies use the same items, vendor, customers, etc why do you need 3 different companies?

Alex_Chow

Savatage wrote:

Question - if all companies use the same items, vendor, customers, etc why do you need 3 different companies?

You know, I always ask this question whenever a client has this request. Here are some responses:
1. Ownerships/investors for different companies
2. Contract obligations and liabilities for each company
3. Tax
4. Marketing and branding for each company
5. Able to sell the other companies off easily

There are probably more that I came across, but that's all I can recall off the top of my head.

p.willemse6

rnunes wrote:

Campy wrote:

Hello,

we have Navision 2009 with 3 Companys.
Now all Companys should have Access to the Customers, Items etc.

Is there any possibility??

Best Regards

Do you want the data to be shared to all companies? If so you have a property on the table (DataPerCompany) and you should put that to no.

Best regards,
Ricardo

NOOOOO!!!!

Alex_Chow

Com'on guys, it ain't that bad. But you DO need to know what you're doing (as to what other tables needs to be shared, etc) and the users will absolutely need to understand the ramifications of sharing master tables (i.e. deleting records) .

An alternative way, as David Singleton suggested, is to create a process to sync the master data and set it to run using the scheduler.

p.willemse6

that's the only way. Sharing data will for sure cause disaster if you don't know what you are doing...

DenSter

Alex Chow wrote:

Com'on guys, it ain't that bad

Yes. It IS that bad. :-k

Just telling people to turn off data per company is the worst advice you can give, because there are 100 things you need to do in addition to turning off that property. It's not rocket science for us, I could probably pull off a project like that (taking care of all tables, come up with a way to set one company as the master company, verify a process with the customer, things like that) off in probably a week, but it is definately NOT as easy as seting one property, which makes that very bad advice.

Alex_Chow

DenSter wrote:

Alex Chow wrote:

Com'on guys, it ain't that bad

Yes. It IS that bad. :-k

But on the flip side, the client wouldn't do this themselves. The NSC would need to make that recommendation and actually do the work to share the tables, so if the NSC is comfortable with it and has experience with it, it's a viable option.

DenSter

I don't know about you, but I have NEVER worked with a customer that did not have the table designer. Any end user reading these posts will think they can do this themselves, and that's when the proverbial s%$t will hit the fan for them.

Say what you want Alex, but you know it is bad advice. I'll let you have the last word on this.

Alex_Chow

Well... The last word is:
If you're an end user, DON'T DO THIS ON YOUR OWN. Ask your NSC for suggestions on your requirements.
If you're a NSC, MAKE SURE you know what you're doing and fully understand the pitfalls.

kine

You can use webservices to sync the data. Question is the needed licensing on that... see Rashed post around this...
viewtopic.php?f=32&t=31476&p=153169#p153169

ara3n

That gives me an idea for the next blog. I'll probably build a solution for this. This has been a weakness in NAV for a long time.

Campy

If you have done it, can you write me a message ?

Can I write a little C# tool thats copies the data in the tables on the sql server ?

ara3n

Campy wrote:

If you have done it, can you write me a message ?

Can I write a little C# tool thats copies the data in the tables on the sql server ?

You will be bypassing all the business rules. unless you use web service.

p.willemse6

kine wrote:

You can use webservices to sync the data. Question is the needed licensing on that... see Rashed post around this...
viewtopic.php?f=32&t=31476&p=153169#p153169

We have been assured accessing NAV from the service tier from another NAV is allowed....

ara3n

Do you have a document? the FAQ does not mention licensing of this kind connection.

p.willemse6

nope, is not in the documents. Was during a conversation with the pricing managers...

ara3n

Have you read this FAQ on webservices?

https://mbs.microsoft.com/partnersource ... es_NAV.htm

It basically states that any connection needs a license.

kine

ara3n wrote:

Have you read this FAQ on webservices?

https://mbs.microsoft.com/partnersource ... es_NAV.htm

It basically states that any connection needs a license.

And question is, if standard NAV user session cover the WebService access too... it means if NAV Session "includes" DCO to access the NAV through WS when the user uses RTC or classic client.

p.willemse6

True, that's why we asked them...