Can we use dimension for privilege?

Speaker
Member Posts: 10
Hi every,
I have two questions in using dimensions.
1.In the function "Chart of account", we can define validate for the three default dimensions such as "optional","Default","Fixed",etc. It's useful when we post a journal with such accounts.
But why can't we find the counterpart in other places? For example, I want to define my vendor "Severn Trent Water" to have mandatory dimension of "IT Department" which means only the IT dept. will buy something from it.
2.Can I go further to band madatory dimension with user's privilege?
For example in my customer, they have severy sales teams to charge different regions. Now, John, the sales for east china login to axapta and place a sales order, can system give him a default dimension value "east china" and can not be changed while Jack has the default value of "north china"?
eager for your aid.
Best Regards,
Speaker Wang
I have two questions in using dimensions.
1.In the function "Chart of account", we can define validate for the three default dimensions such as "optional","Default","Fixed",etc. It's useful when we post a journal with such accounts.
But why can't we find the counterpart in other places? For example, I want to define my vendor "Severn Trent Water" to have mandatory dimension of "IT Department" which means only the IT dept. will buy something from it.
2.Can I go further to band madatory dimension with user's privilege?
For example in my customer, they have severy sales teams to charge different regions. Now, John, the sales for east china login to axapta and place a sales order, can system give him a default dimension value "east china" and can not be changed while Jack has the default value of "north china"?
eager for your aid.
Best Regards,
Speaker Wang
0
Comments
-
Hi,
Yes, u can do both of them with a little work and inspiration. For both problems, you will create a DimensionSetup table with rules, having the following fields:
TableId, FieldId, Value, Dimension1Mandatory, Dimension1Default, ... DimensionXMandatory, DimensionXDefault.
Then you create the records. E.g.: for vendors,
tablenum(vendTable), fieldnum(vendtable,name), NoYes::yes, 'ITDepartment', ...
Then in the VendTable.validateWrite(), you put a condition like:
if (DimensionSetup::find(tablenum(vendtable),fieldnum(vendtable,name),this.name))
{
this.dimension[1] = dimensionSetup::find(..).dimension1default;
(...)
}
The same for Sales man - replace vendtable with employee, and so on.
Cheers,
CiprianKind regards,
Ciprian Dudau
Axapta Developer0 -
Hi there,
Try to specify dimension against the vendor in the Vendor table. Once this done, all subsequent transactions of this vendor should have the dimension.
Likewise you can try creating sales people as internal customers (identified by separate customer group).
Hope this helps,
Harish MohanbabuHarish Mohanbabu
Long way to go before I sleep..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