Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 295 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Any suggests for DataPerCompany=no ?
gianus
Member Posts: 22
Scenario:
Two very small trading companies (12 and 5 Users)
Same business, same building, same fin & adm. employees,
same Items, almost same customers, almost same vendors.
No granules about production, service, human resources, only financial, sales & marketing, purchase, warehouse.
Any of You can suggest me upon in which table is convenient to set to "no" the DataPerCompany property?
Apart some table as Post Code, Territory, Country, Currency, obviously setted to "no" and
some tables as each "entry" obviously setted to "yes"...
Thank You all in advance.
Two very small trading companies (12 and 5 Users)
Same business, same building, same fin & adm. employees,
same Items, almost same customers, almost same vendors.
No granules about production, service, human resources, only financial, sales & marketing, purchase, warehouse.
Any of You can suggest me upon in which table is convenient to set to "no" the DataPerCompany property?
Apart some table as Post Code, Territory, Country, Currency, obviously setted to "no" and
some tables as each "entry" obviously setted to "yes"...
Thank You all in advance.
Gianni Capra
www.exe.it
www.exe.it
0
Comments
Second, it's complicated. Especially once you start dealing with dimensions. For example, a master record that has dimensions. You share the master table, but forget to share the Default Dimension table. Suddenly the master record says something completely different from the Dimensions table in one company, but matches the other.
My Blog - nav.education
Just .... Don't .... Do .... It !!!!!
But as for multi-company tables they're rarely worthwhile, except for super-static tables.
The dimension and dimension value tables sometimes work. Beware deletes.
The number series tables are also a possible candidate; but only for small databases, or with block-free changes.
Always, the possibility of deletes in one company making links in another company invalid is a problem and a pain to detect.
TVision Technology Ltd