I guess this error message can make sense for sure, but not with what I was doing today.
I mean, working with the new document reporting feature in NAV 2015, this perfectly would made sense importing a Word layout, that has just been updated, but in such a way that is ended up to be malformed .
But this wasn't what I was doing. At least that's what I thought and also proved to be so.
What did I do to get here?
From C/SIDE I had exported the Word layout of REP1306. Opened it in Word…

As Mark started to set the pace , I am following up on this with my list of small enhancements that could easily be picked up in the next release. Let's clean up NAV from obsolete remnants. I just call this post #1 even though I am totally unaware how many more will follow.
So here we go: 'Houston' ... uhhh ... 'Vedbeak' let's get rid of the obsolete report property URL and function SAVEASHTML .
For those who agree, give your vote here .

Last week performing a NAV 2013 update training, I was confronted with the above message when opening the layout from C/SIDE in Visual Studio 2013. "Ouch", I thought, "apparently trusting too much on my installation to work well. Should have checked." Surely after my laptop re-install some weeks ago.
"OK, let's click OK and see," I said to myself, crossing fingers. Luckily Visual Studio opened up showing me the layout of the report and indeed a useful message in the output window:
Typically…