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
- 297 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
Report defaults different by caller
njhansen
Member Posts: 37
Is there some way to access the call stack in C/AL code?
I've got a report that is called (several layers deep) from a codeunit running in a periodic job started from NAS. I would like its default behavior (date range) to be different if it is running automatically than if a user ran it from a menu.
The closest I can get is to check GUIALLOWED in the report to see whether I'm running from NAS, but there might be times that the same codeunit gets run by a person (for testing), and it would be preferable if the behavior were based on whether the call originated with CU nnnnn, not whether it was actually NAS that started it.
Because of some generic wrapper functions in the call stack, it would be a significant pain to try to filter a record and pass it to the report.run.
Other thoughts:
CU nnnnn sets a Boolean in a setup table somewhere, but that affects everyone system-wide
CU nnnnn creates a dummy file on the client's machine, but that affects all NAV clients running on the machine, and might cause permissions problems
I've got a report that is called (several layers deep) from a codeunit running in a periodic job started from NAS. I would like its default behavior (date range) to be different if it is running automatically than if a user ran it from a menu.
The closest I can get is to check GUIALLOWED in the report to see whether I'm running from NAS, but there might be times that the same codeunit gets run by a person (for testing), and it would be preferable if the behavior were based on whether the call originated with CU nnnnn, not whether it was actually NAS that started it.
Because of some generic wrapper functions in the call stack, it would be a significant pain to try to filter a record and pass it to the report.run.
Other thoughts:
CU nnnnn sets a Boolean in a setup table somewhere, but that affects everyone system-wide
CU nnnnn creates a dummy file on the client's machine, but that affects all NAV clients running on the machine, and might cause permissions problems
0
Answers