ArcherPoint Dynamics NAV Developer Digest – vol 44
The ArcherPoint technical staff—made up of developers, project managers, and consultants – is constantly communicating internally, with the goal of sharing helpful information with one another.
As they run into issues and questions, find the answers, and make new discoveries, they post them companywide on Yammer for everyone’s benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this group—so we thought, wouldn’t it be great to share them with the rest of the Microsoft Dynamics NAV Community? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from the ArcherPoint staff. We hope these insights will benefit you, too.
Faithie Robertson on showing variable values in RDLC reports:
One of our clients requested that we show a value on an RDLC report with the old classic format for decimal positions of 2:5 and also don't show a number at all if it's zero. In case you're not familiar with 2:5, it will show a minimum of 2, but can show 3, 4, or up to 5 decimals while dropping any trailing zeros.
My report field is calculated in the Report RDLC Code, so there wasn't a field from the Report Designer available to use a "=Fields!FieldnameFormat.Value" expression. And even when I did try a different field's format, since the field is calculated in RDLC, it just ignored my entry (the nerve!).
So naturally, I called Michael Heydasch, ArcherPoint's RDLC Expert Extraordinaire, PhD RDLC, and he showed me how to use the VB FORMAT function. After a little adjustment, here's the format that works:
Just put that in the Custom Format field on the Textbox Properties under Numeric and you're good as gold...just like Michael!
Note that there are three sections to the format separated by semicolons. The first is for positive values, the second for negative values, and the third for zero values. (Who knew you could set three different formats based on the values!) Here's the link to the FORMAT function in case you want to be creative.
Cory Power shared this PCWorld article on Skype for Business replacing Lync:
Microsoft is doing away with Lync as we know it and going instead with "Skype for Business". Read the article:
Alan Campbell shared these links on resolving project backlogs in an Agile project:
The need to standardize and prioritize the handling of the product backlog is an important step for the client, project managers, and the development team. This set of articles offers practical advice on what the issues are and recommends a methodology to handle them. A good read.
From the article:
“The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order, estimate and value.”
From my perspective there are a variety of factors that should influence priority:
- Customer value (right problem solved)
- Business value (revenue generated)
- Technical value (fosters learning, reduces risk, solid solutions, intelligent workflow)
- Quality value (mitigated risk or improves quality)
Read the entire article: