Howdy, Stranger!
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
- 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
- 304 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Column Set hard coded in Analysis by Dimension on RTC Client
Pooja
Member Posts: 16
Hi Experts,
I have found the that the no. of columns to be displayed on RTC client in Analysis by dimension is limited to 32 columns. I have checked and found that this is hard coded.
If i have more than 32 columns to display system is not showing however it is working fine in classic. Has anyone else faced this problem and how has it been handle. And could be the reason for such hard coding.
Regards,
Pooja
I have found the that the no. of columns to be displayed on RTC client in Analysis by dimension is limited to 32 columns. I have checked and found that this is hard coded.
If i have more than 32 columns to display system is not showing however it is working fine in classic. Has anyone else faced this problem and how has it been handle. And could be the reason for such hard coding.
Regards,
Pooja
0
Comments
If i have more than 32 columns to display system is not showing however it is working fine in classic. -not entirely true, it can only display 32 columns at the same time. But navigation tools allow more columns to be accessed.
Has anyone else faced this problem and how has it been handle. - I haven't experienced a problem with it. It's because Matrixes was native in NAV Classic, but could not be remade in the RTC/C# with the direction the team was taking in design of pages/. Microsoft has offered this 32 columns matrix as a solution for matrixes in RTC.
And could be the reason for such hard coding. - what you see in the hard coding is actually what happens behind the scenes in a regular matrix form.
However the cap of number of columns visible for 1 classic matrix form will probably be datatype limited instead of variables limited. - opinion
|To-Increase|
I have never heard of anything called Navigation tools in Navision. What are you refering to?
I have never heard of anything called Navigation tools in Navision. What are you refering to?
I refer to the matrix controls's arrows to either move forward or backward in the dataset1: the columns. Because you navigate trough the dataset, I just called it navigation tools.
|To-Increase|
But is there a way to export all the columns in excel instead of only 32 columns at a time...as users will not agree to use Navigation Tool ](*,)
And what do you mean, users won't use navigation tools to examine the entire set? Do your users never use a scrollbar, or a button to go to a next page? Because that is exactly what you are claiming now.
What you seem to miss is that the design of that matrix replacement page is control design.
It does not corrolate to the data itself. If an export was buildin, it would not export just 32 columns, but would export all the columns.
|To-Increase|