NAV 2015

Any clue about cue?

  • Post comments:5 Comments
  • Reading time:4 mins read

Do you know cues? Those clickable colorless stacks of documents in NAV 2009, that turned into clickable blue stack tiles in NAV 2013 R2, and that worked on top of FlowFields of type Integer?

Well, in NAV 2015, this munch bunch has turned into clickable blue tiles with pictures and colorful indicators that are configurable per user, that work on top of any kind of numeric fields (normal or abnormal), or better yet, on top of any kind of numeric expression (you can bind them to RANDOM(1000) for all NAV cares).

(more…)

Continue ReadingAny clue about cue?

Upgrade Codeunits in NAV 2015

  • Post comments:10 Comments
  • Reading time:9 mins read

Once upon a time, and really not such a long time ago, there was no such thing as a codenit type. In all honesty, there is still no such thing as a codeunit type – there is subtype, though. (Why we have subtypes, without having types, beats me, but let’s let the semantics go.)

Nowadays, we have four codeunit types. NAV 2009 SP1 brought along the Test and Test Runner types, which – in my experience, at least – haven’t seen much runtime (which is a pity, if you ask me). And now NAV 2015 brings along another type: the Upgrade codeunit type. The mere sound of it makes my heart thrill. The Upgrade codeunit. Mmm.

(more…)

Continue ReadingUpgrade Codeunits in NAV 2015

Synchronizing Database Schema in NAV 2015

  • Post comments:6 Comments
  • Reading time:5 mins read

Before NAV 2013 R2 the “database schema synchronization” was an unknown term. Either you could do a database schema change, or you couldn’t. There was no such thing as data loss.  If you wanted to change a field type or delete a field (or delete the whole table for that matter), and there was data in that field in the table, you got an error. Data present – no go.

However, with multi-tenancy, and the possibility to mount tenant databases originating from different applications, suddenly there was an issue – how should NAV handle possible differences in database schema for different tenants? Should we force the change at the cost of data loss? And thus the term “database schema synchronization” entered the vocabulary of regular NAV Joes.

(more…)

Continue ReadingSynchronizing Database Schema in NAV 2015