All around NAV dev and test
... you still can for the first DDC event in 2011 (and the second ever ).
As we communicated before, this time we will have 2 sequential sessions and contrary to our first event this will NOT be a purely technical happening.
The first session will be performed by Arne de Booij, Senior UX Researcher at Microsoft for the Dynamics product family. In this session Arne will shed light on the background of the role-based thinking and,based on the results of a survey among more than 15 companies in multiple countries, illustrates how Role Based client of Microsoft Dynamics is used in day-to-day business.
Send us a e-mail: email@example.com with the following details:
When was your last time facing this screen?
Mine was last week. And then I took the screen shot and decided to write a blog on it. Or actually, I had even decided on that way-before as this "feedback" screen keeps on appearing every now and then. Even those days-after every time I dutifully did "help".
I guess I can cope with that Usability Sciences stalker. I can cope with the fact that for every search I do on PartnerSource I have to relearn how to find what I am looking for. Fortunately I am using it daily. Also fortunately for my colleagues who often refer to me when they have to use PartnerSource.
So when I give feedback I can positively answer all questions as I do find what I am looking for; and, yes, I am using it frequently; and, yes, it makes sense to use it; and, .... And PartnerSource stays as it was.
I have no proof, but it seems to me PartnerSource hasn't changed since it started as PartnerGuide. Probably it has, but not much. At least is doesn't make me happy.
It's all so inefficient, counter-intuitive, so opposite to the user experience of MS product.
Just a small example. Ever created a support request? If you select Support > New Support Request you get to a screen with this section:
So I push the blue (NAV) button. And on the next page I will push this button:
Which lead me to the start of my new support request.
I select the company and click next.
Didn't I select NAV already?
Am I wrong assuming that all I am writing about PartnerSource also applies to CustomerSource?
Want to share your experiences, judgements and suggestions: write them below, MS seems interested; they contacted me on this!
The above example still hasn't been improved.
MS seemed interested though.
More than 1 year passed and still the above example hasn't been improved.
.. not a "normal" release ... beware!, Waldo informed us on his blog almost 2 weeks ago.
This post is just to add some info on the things I encountered today. No big issues (so far), but some minor, mainly translation matters.
Comparing R2 NL with NAV 2009 SP1 NL showed me that:
Next to these two errors I stumbled over two other issues:
This altogether makes me wonder if other local version suffer from the same kind of issues.
... unless your have a good reason for it!
Already a year ago I wrote my Validating Data series. And only a couple of weeks ago me and my colleague were investigating one of our solutions that had a performance issue and were faced with code that wasn't quite SMART with respect to using VALIDATEs. If you're not sure what I am referring to (re)read this post: Validating Data #4: Assignment and VALIDATE.
And there we were sitting. Me wondering how an intelligent developer could have done this. My colleague (not his code; not mine either) wondering what actually was wrong about it. As became clear we both were looking from a very different perspective at these lines of code where a number of fields were populated and validated at the same time.
My perspective based on the rule-of-thumb saying: Never use VALIDATE ... unless you have a (very) good reason for it. Or, quoting Marq in my post, "... to avoid the validate statement when populating records ...".
My colleagues rule-of-thumb: always validate a field when assigning a value, because you're never sure validation code is behind it.
I (still) think I could make my point and could clarify that his rule-of-thumb is definitely not a good enough reason to use VALIDATEs. So I would like to stress to you all again:
Never use VALIDATE ...
... unless you have a good reason for it.
If you're not sure what I mean or disagree. Read my Validating Data series and challenge me below.
... dimishing the number of VALIDATE statement in our code did help, but (unfortunately) wasn't the main problem.
After you did read this post be sure to read the comments below as I wrote it because of the discussion. And of course, if you did not read my Validating Data series yet take your time for it.
With this BaIS sequel I am going to create a collection of findings and thoughts on the various things we are coming across within Imtech ICT during our quest in building international solutions. Findings and thoughts not always logically ordered, but worth sharing with and getting comments on from the Dynamics community. So be invited to comment on them.
Possibly this might lead to some sort of white paper on BaIS and Dynamics NAV, who knows.
Building international solutions with multiple developers for multiple countries places us for the challenge how to manage/control our code. This is not only about how we secure the code and the change history, but also about how to propagate changes from the international code to local code, i.e. from our w1 to, let's say, to a UK version. Or even from our horizontal solution into various vertical solutions. Altogether we need a source control system that:
As Dynamics NAV does not have an on-board source control system and no NAV-aware source control system seems to exist that can cover our need, we had to do it with existing systems. First of all this forces us to store our code (objects) in .txt format. Not a big problem as such, but of course no standard tool now that can check the syntax of my code. But OK, I can live with that. I have done it at MS for many years already.
No captions should be stored in the code objects. For a number of reasons:
As might have concluded from a number of my other posts we decided to take Visual Studio Team Foundation Server as our source control system. We are working with it and the same time still investigating. Too early to share things on that so one of the upcoming BaIS posts will probably be dedicated to that.