Set filter for table lookup on Request Page

Roelof
Member Posts: 377
I want to set a table filter for a lookup (or drilldown) on a table, like the Customer table, for a Request Page on a report.
I want to set filter: 'Customer Posting Group' so that only customers for that posting group will show up in my lookup.
I want to do the lookup for the Customer.'No.' field. The field is added to the ReqFilterFields on the Customer.DataItem of the report.
I have set the 'Customer Posting Group' filter in the Request Page.OnOpenPage trigger. But it has no impact.
I do know that the same can be achieved by adding a dedicated Customer No. field on the Request Page and add functionality to the field trigger(s) with a page call and settableview, etc.... but the problem there is that I can't set a range, since each time, after you have set the Cust.No for the 'Begin-range' and go back to the lookup page to find the next customer no. for the end-range (like 100..200), the first custno (Begin-range) dissappears. You wouldn't have that for doing a lookup from a field, defined in the ReqFilterFields.
Any idea if it's possible?
Thanks.
I want to set filter: 'Customer Posting Group' so that only customers for that posting group will show up in my lookup.
I want to do the lookup for the Customer.'No.' field. The field is added to the ReqFilterFields on the Customer.DataItem of the report.
I have set the 'Customer Posting Group' filter in the Request Page.OnOpenPage trigger. But it has no impact.
I do know that the same can be achieved by adding a dedicated Customer No. field on the Request Page and add functionality to the field trigger(s) with a page call and settableview, etc.... but the problem there is that I can't set a range, since each time, after you have set the Cust.No for the 'Begin-range' and go back to the lookup page to find the next customer no. for the end-range (like 100..200), the first custno (Begin-range) dissappears. You wouldn't have that for doing a lookup from a field, defined in the ReqFilterFields.
Any idea if it's possible?
Thanks.
Roelof de Jonghttp://www.wye.com
0
Answers
-
1. OnOpenReport is your right trigger for setting filters
2. You have to insert code in OnLookup trigger in Request page0 -
Hi Lubost,
Sorry, no, that is not the problem. I'm aware of these settings.
The problem is the lookup. Even though the filters are defined (where ever you define it, like OnOpenReport trigger or through additional code in the OnLookup trigger on the Request Page, or different areas), it does not have impact on the lookup of the field, defined in the ReqFilter fields property of the DataItem. It is not taking any filters in consideration.Roelof de Jonghttp://www.wye.com0
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