Problem with refreshing RequestPage
biant123
Member Posts: 29
Hi,
I have created a report with Request Page, on the Request Page,
there are 1 Option field called Type with OptionString: Import,Export
and 3 boolean fields called Mode 1, Mode 2, Mode 3
When user select Export from the Type, I would like to set the 3 boolean fields to invisible.
I have set the Visible property of the 3 boolean fields with a variable called HideIt. And set HideIt property IncludeInDataset to Yes.
On the Type - OnValidate trigger and OnOpenPage, the HideIt value will be assigned according to Type selection by the user.
But still the Request Page is not refreshed and remain the same when Type is changed
. Is there anything missed out here? Any suggestion will be appreciated. Thank you.
I have created a report with Request Page, on the Request Page,
there are 1 Option field called Type with OptionString: Import,Export
and 3 boolean fields called Mode 1, Mode 2, Mode 3
When user select Export from the Type, I would like to set the 3 boolean fields to invisible.
I have set the Visible property of the 3 boolean fields with a variable called HideIt. And set HideIt property IncludeInDataset to Yes.
On the Type - OnValidate trigger and OnOpenPage, the HideIt value will be assigned according to Type selection by the user.
But still the Request Page is not refreshed and remain the same when Type is changed
0
Answers
-
Did you try directly in page or transformed it?
Did you try by making it editalbe and non editable?0 -
Hi Mirko,
Thanks for your suggestion, it does grey-out if i set it at Enabled. But just wondering how does the mechanism behind work that it able to grey-out with Enabled property but not able to hide the text box and label with Visible property?
Hi Mohana,
Thanks for your reply. I directly created the report with a request page.0 -
NOTE: I'm not 100% sure about this, it's based on something i've read here and there...
what is not visible when opening page, is not retrieved by the client (e.g. page based webservices can only "see" VISIBLE fields). Managing the visibility property dynamically after the page is open enforce nav to make additional roundtrips between client and server, thus degrading performance (incremented network traffic).0 -
Just an input - you can't control the visibility of a field BUT you can control the visibility of a Group
-Mihail- [MCTS]0 -
Hi Mihail, you are right, thanks for the brilliant idea! :thumbsup:
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
