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
NAV2015 EvaluationMode attribute in every RDLC Value element
davorp
Member Posts: 17
Has anyone else noticed that NAV 2015 Development Client seems to be adding an EvaluationMode attribute to every Value element during compilation phase after receiving RDLC file from Visual Studio?
This is causing a lot of unnecessarily changed lines in RDLDATA part of the NAV object.
For example - standard NAV W1 object might have this:
This was not the case with NAV 2013 R2, and is happening on both NAV 2015 RTM W1 development environment as well as on CU5 build 40262.
I'm also pretty sure it's not Visual Studio's fault since the file VS is saving in TEMP directory before NAV client takes over doesn't have this attribute inserted (unless it was already there)
Can anyone else confirm this?
This is causing a lot of unnecessarily changed lines in RDLDATA part of the NAV object.
For example - standard NAV W1 object might have this:
... <Value>=Parameters!IntrastatJnlLineTypeCaption.Value</Value> ...and when you open Report in Designer, edit Layout in Visual Studio, change something (or not...) then recompile and save RDLC in Visual Studio so that NAV client picks up changes and saves a new object, the modified object now has attribute EvaluationMode = "Auto" added to each and every Value element (hundreds of them, even the empty ones!), as in:
... <Value EvaluationMode="Auto">=Parameters!IntrastatJnlLineTypeCaption.Value</Value> ...According to MSDN, EvaluationMode attribute already has a default value of "Auto" so I don't see the need for it to be added to Value element.
This was not the case with NAV 2013 R2, and is happening on both NAV 2015 RTM W1 development environment as well as on CU5 build 40262.
I'm also pretty sure it's not Visual Studio's fault since the file VS is saving in TEMP directory before NAV client takes over doesn't have this attribute inserted (unless it was already there)
Can anyone else confirm this?
0
Comments
Additionally, it's excessive to get added. According to docs, AUTO is the default option: https://msdn.microsoft.com/en-us/librar ... (v=sql.105).aspx
CEO, Spare Brained Ideas, Göteborg, Sweden
New (April 2021) Getting Started with Microsoft Dynamics 365 Business Central Book Available: "Your First 20 Hours with Business Central"
What's puzzling is that W1 (World release) NAV objects out of the box don't have this element, only when you change RDL and recompile does it get added.
Perhaps this is an unwanted feature of some sort, since it doesn't make much sense otherwise...
Are you saying that you have trouble running RDLC reports in non ENU languages because of EvaluationMode element?
If you have the same report in different NAV versions you end up with tons of differences because of this default value....
Is there a way to avoid this?
RDLC in .txt always sucked (when upgrading) and now it sucks even harder. Someone likes sucking overthere