Limitation on Nested IF THEN ELSE statement in NAV 2016

DRB · 2016-01-14

Hi,

Interesting observation related to NAV 2016:

Seems there is limitation on Nested IF THEN ELSE statement, you can do upto 35 cases and if done on 36th case then NAV crashes while compiling the object.

Although there was no such limitation upto NAV 2015. I know one should use CASE OF statement in such scenarios, but this issue initially appeared little weird.

Did anyone else also faced this issue and is it documented FEATURE in NAV 2016?

andrewt · 2016-01-14

Although crashing the client doesn't sound like a documented feature but more like a bug, you should take 'Cyclomatic Complexity' into account on your dev tasks anyhow.
This has been focused as a design pattern by Microsoft since the release of NAV 2015 and has been implemented as a general design guideline which should be followed by us as developers.
https://community.dynamics.com/nav/w/designpatterns/175.cyclomatic-complexity

Cheers
Andrew T.

DRB · 2016-01-14

@Andrewt, I know it is a bug but not feauture, but wrote FEATURE sarcastically !!!

andrewt · 2016-01-14

I know you know so we both missed to use

, don't we ?
Anyhow, my comments regarding 'Cyclomatic Complexity' (oh man, I love this term...) were genuine, so although it seems to be a bug (haven't yet verified by myself) it seems to be more theoretical as we wouldn't get there as long as we follow these reasonable design patterns and guidelines.

Cheers
Andrew T.

Miklos_Hollender · 2016-01-14

It is their subtle way of telling you to never even think about coding like this

Belias · 2016-01-14

Moreover...there's nothing more crashy than nav2016 development environment
(but for sure, the point is: "why in the heck there are 36 IFs? O.o i'd like to see them indented in nav 2009

)

Limitation on Nested IF THEN ELSE statement in NAV 2016

Answers

Categories