Different Objects for different Companies in one DB

Asiri
Member Posts: 26
Hi,
In Navision within one DB can create multiple Companies. If we do any change into one object (ex. Customer Card, add a new field) in one Company it will effect to the other Companies also (it can see in the other companies Customer Card also). Is there any way to handle this situation by not appearing one company object changes to other companies.
Your response is highly appreciated.
Warm Regds,
Asiri
In Navision within one DB can create multiple Companies. If we do any change into one object (ex. Customer Card, add a new field) in one Company it will effect to the other Companies also (it can see in the other companies Customer Card also). Is there any way to handle this situation by not appearing one company object changes to other companies.
Your response is highly appreciated.
Warm Regds,
Asiri
0
Comments
-
The only way to handle this is to create two objects and create AL code to handle the call's. However this is not recomended. Recommended is to keep the same objects.
For very small changes you can influence the apearance of a form by AL code like currform.control.visible or currform.control.xpos/ypos.
Sorry.0 -
I share the opinion of Mark. Only very small adjustments should be made. Sales documents, etc. is a an exception.
By the way, you can distinguish the companies with the system constant COMPANYNAME.
Thomas0 -
Yes, most reports can be controled using the report selections. This way you can change the invoice layout per company. Make one report in the object designer for each layout.0
-
Just briefly: If you run on SQL Server it is technically possible to have multiple sets of objects in the database; e.g. a different versions of table 36 without adding a new table with "Object Designer".
The trick is to copy the "Object" table - as many times as you wish - and then point to the different sets (Object tables) on demand, by modifying the "identifiers" in table $ndo$dbproperty ...
But implementing this properly is really tricky business, and if done wrong you'll definitely screw up your system ...
Just for "inspiration" :-k
So, you should stick to the options mentioned by Mark and Thomas!Jörg A. Stryk (MVP - Dynamics NAV)
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool0 -
Hi Thks a lot for your comments, it's greatly appreciate.
Thks again, Mark, Thomas & Jorg.
Best Regds,
Asiri0 -
One table can link with only one "LookupFormID", even if we create seperate objects same lookup form will popup if the user press F5. (Ex. Customer table "LookupFormID" link with "Customer List". if we create seperate Customer Cards even if the user press F5 in Customer card same "Customer List" will popup).
Can we customize this table "LookupFormID" property?0 -
No, you cannot, but you can add your own C/AL code into OnLookup trigger and call what you want...0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions