Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
Options
NAV 2015 Bug? TableRelation and Enabled with condition
HeinziTuberkel
Member Posts: 4
Recently I encountered a reproducable NAV 2015 client crash that took me a while to understand.
Table "A" contains a field "Ref B"(Code 20) that is used to reference Table "B". Therefore the Field "Ref B" has its property TableRelation to "Table B"."PK Field".
Page "Card A" uses table "A" as SourceTable.
An action "Show Card B" opens RunObject "Page Card B" with RunPageLink "PK Field"=FIELD("Ref B").
This works without problems.
Now I wanted to disable the Action as long as the Link to Table B is empty. So I added a check to the action's "Enabled" property:
"Ref B"<>''
From now on the NAV Client crashes (=closes without any notice) as soon as I try to open Page "Card A".
Everything works fine if i either
- remove the condition from Enabled in tha action or
- remove the TableRelation from Table "A"
Is this a known bug? Does it persist in newer NAV (or Dynamics) versions?
It there a workaround (aside from removing one or the other)? ;-)
Table "A" contains a field "Ref B"(Code 20) that is used to reference Table "B". Therefore the Field "Ref B" has its property TableRelation to "Table B"."PK Field".
Page "Card A" uses table "A" as SourceTable.
An action "Show Card B" opens RunObject "Page Card B" with RunPageLink "PK Field"=FIELD("Ref B").
This works without problems.
Now I wanted to disable the Action as long as the Link to Table B is empty. So I added a check to the action's "Enabled" property:
"Ref B"<>''
From now on the NAV Client crashes (=closes without any notice) as soon as I try to open Page "Card A".
Everything works fine if i either
- remove the condition from Enabled in tha action or
- remove the TableRelation from Table "A"
Is this a known bug? Does it persist in newer NAV (or Dynamics) versions?
It there a workaround (aside from removing one or the other)? ;-)
0
Answers
Unfortunately, this does ... once again ... not work for me because I only have the "Designer" licence, which allows me to add fields and properties but keeps me from adding code (and variables) into table or page objects.