Set editability of a table field based on a condition
aquinco
Posts: 16
Hi everyone.

Can anyone answer this question:
Can I set one table field to be editable if user chooses "option 1" in previous field and non-editable if "option 2" is chosen?
I know that I can easily define variable IsEditable and set it in editable property when creating pages, but can something like this be done on tables?
Thanks!!!
Can anyone answer this question:
Can I set one table field to be editable if user chooses "option 1" in previous field and non-editable if "option 2" is chosen?
I know that I can easily define variable IsEditable and set it in editable property when creating pages, but can something like this be done on tables?
Thanks!!!
0
Best Answers
-
You can check the variable based on record in onOpenPage and OnAfterGetRecord by creating a function which return True or False.
Thanks & Regards,
Saurav Dhyani
Do you Know this About NAV?
Connect - Twitter | Facebook | Google + | YouTube
Follow - Blog | Facebook Page | Google + Page5 -
On Card pages you could just straight up set those fields to invisible based on your condition.
Don't do conditionals like this on a table basis, try to get around it on the page itself.Austrian NAV/BC Dev5
Answers
-
why do you need it in tables?
I guess, if you write code in table field onvalidate then it should work0 -
Hey,
I dont think you can play with these stuffs on Tables. As in Tables you have strictly Yes or Not as in Editable Property.
Still have a question why you want this on Tables, Users will have access to Pages.Thanks
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/0 -
Well, my mentor wants me to do this -.- But it's good to know I can only do this on Pages.

Where should I set conditions for my variable IsEditable besides OnValidate trigger for mentioned field?
Thanks! 0 -
You can check the variable based on record in onOpenPage and OnAfterGetRecord by creating a function which return True or False.
Thanks & Regards,
Saurav Dhyani
Do you Know this About NAV?
Connect - Twitter | Facebook | Google + | YouTube
Follow - Blog | Facebook Page | Google + Page5 -
On Card pages you could just straight up set those fields to invisible based on your condition.
Don't do conditionals like this on a table basis, try to get around it on the page itself.Austrian NAV/BC Dev5
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
- 611 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 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


