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
Currpage.LOOKUPMODE not working in page
oki
Member Posts: 46
Hi,
does anyone know why the global property CurrPage.LOOKUPMODE isn't set if the page is opened via a lookup/drilldown from a referenced field?
Example:
Open Customer Card. Click on the lookup/drilldown arrow of the Salesperson/Purchaser Code field. This opens the Page14 Salesperson/Purchaser list.
But in the OnOpenPage Trigger the property CurrPage.MOOKUPMODE is always false. (tested with MESSAGE function)
I intend to set some filters in the OnOpenPage Trigger if the page opens in LOOKUPMODE.
Has anyone an idea?
Thanks in advance
Oli
does anyone know why the global property CurrPage.LOOKUPMODE isn't set if the page is opened via a lookup/drilldown from a referenced field?
Example:
Open Customer Card. Click on the lookup/drilldown arrow of the Salesperson/Purchaser Code field. This opens the Page14 Salesperson/Purchaser list.
But in the OnOpenPage Trigger the property CurrPage.MOOKUPMODE is always false. (tested with MESSAGE function)
I intend to set some filters in the OnOpenPage Trigger if the page opens in LOOKUPMODE.
Has anyone an idea?
Thanks in advance
Oli
0
Comments
have you find a usefull workaround? I've the same problem.
max
A colleague of mine had the same issue and couldn't find a workaround. As this worked fine in the classic client with forms (CurrForm.LOOKUPMODE) then we considered this a bug and reported it to Microsoft. The support engineer has replicated the issue and has escalated to development to see what they say - whether it is a bug or not! It's been with them for a while now, no progress yet but fingers crossed they will fix this soon.
Regards
Kishor
thanks for your reply. I have it also reported to Microsoft and they told me nearly the same. So let's pray, that they fix it...
(As I know the bug exist from the first RTC Client till NAV2016)
Max
try this Solution ...beginnersnav.blogspot.in/search/label/INPUT%20Box
Raja Venkat
https://beginnersnav.blogspot.in/