Microsoft - RTC Reports
Ravi_Thakkar
Member Posts: 392
Hello All,
I have some queries related to RTC Reports provided by Microsoft.
1) Why Microsoft Developed RTC Reports, are not in proper Layouts?
2) How to manage, CODE LOGIC in RTC Reports written on SECTIONS in CLASSIC?
3) How to manage Controls in RTC Reports exists on TRANSHEADER and TRANSFOOTER section in CLASSIC Reports?
4) To develope RTC Reports, CLASSIC Reports are MUST to be developed due to DATASETFIELDNAME. Why should we require Double work? Any solution?
5) VARIABLES are not accessible in VISUAL STUDIO during development until they are assigned to seperate CONTROLS (Textbox) in CLASSIC. Any Solution?
Please, provide me according solution or suggestion.
I have some queries related to RTC Reports provided by Microsoft.
1) Why Microsoft Developed RTC Reports, are not in proper Layouts?
2) How to manage, CODE LOGIC in RTC Reports written on SECTIONS in CLASSIC?
3) How to manage Controls in RTC Reports exists on TRANSHEADER and TRANSFOOTER section in CLASSIC Reports?
4) To develope RTC Reports, CLASSIC Reports are MUST to be developed due to DATASETFIELDNAME. Why should we require Double work? Any solution?
5) VARIABLES are not accessible in VISUAL STUDIO during development until they are assigned to seperate CONTROLS (Textbox) in CLASSIC. Any Solution?
Please, provide me according solution or suggestion.
0
Comments
-
1) What is "proper layout"?
2) Behind section trigger you should have only code regarding visibility of the section. All this is executed, the resulting dataset is created from all visible sections.
3) See the NAV blog, there is article about transfooter and transheader. http://blogs.msdn.com/b/nav/archive/201 ... ports.aspx
4) Yes, it is in this way to have solutions, where partners can easilly transit from classic client to RTC without "big jump". Using "build from scratch" will be more challenging... but that it is in this way now doesn't mean that it will be in next version. This is going to be changed in NAV "7".
5) You have written the solution yourself. Add the variable as editbox on som section and set it as Visible=No.0 -
Thank you Kamil for your Reply and Solution/Suggestions.kine wrote:1) What is "proper layout"?
2) Behind section trigger you should have only code regarding visibility of the section. All this is executed, the resulting dataset is created from all visible sections.
3) See the NAV blog, there is article about transfooter and transheader. http://blogs.msdn.com/b/nav/archive/201 ... ports.aspx
4) Yes, it is in this way to have solutions, where partners can easilly transit from classic client to RTC without "big jump". Using "build from scratch" will be more challenging... but that it is in this way now doesn't mean that it will be in next version. This is going to be changed in NAV "7".
5) You have written the solution yourself. Add the variable as editbox on som section and set it as Visible=No.
1) For Proper Layout refer the attached.
Attached an image of Classic as well as RTC Report views for Report ID 2.
That shows differences. (There are so many such)
1-Data Issues (not getting same in Both)
2-Data Allignment not same at some places
3-Field sizes not same.
I have shown just an example. There are Sooo many reports having such issues.
That means, If we are providing RTC to any customer then we are not able to Provide them RTC Reports without testing and modifying many Reports.
Kamil, Thank you very much for your help in other Points.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
