Application Area property in Navision 2017

zohaibu95@hotmail.com

Hi Guys,
I have just read about the "Application Area" property in dynamics nav 2017.
Can you tell me what is its purpose and what is the purpose of

#All
#Basic
#suite?

Please elaborate in easy words. Thanks

Juhl

Leave it blank in NAV.
It's used in 365 for now, and not implemented in NAV

zohaibu95@hotmail.com

Juhl wrote: »

Leave it blank in NAV.
It's used in 365 for now, and not implemented in NAV

I wanted to know for Dynamics 365 because i am creating app for Dynamics 365 that is why asking.

Juhl

But the intent is visual grouping, so a sales persons sees some fields, and a warehouse employee sees other fields on a given page. Not to be mistaken for security.
So dynamic views.

Configure Profiles instead, does the same and works.

zohaibu95@hotmail.com

Ok cool. Btw if we leave the Application Area blank will it still work for Dynamics 365?

Juhl

Yes, visible to all users.

zohaibu95@hotmail.com

OK THanks

mohana_cse06

Leaving it blank doesnt seems to be correct.

If you read the technical validation pdf provided by MS then they made this property mandatory.

If user selects basic/suit in D365 then fields/controls with blank application area won't show.

You need to decide based on your app area.

If your app is based on jobs module then you need to set #suit because standard jobs module will be shown in suite mode only.

janpieter

I actually like the idea of application area's. Granted it is poorly executed because in my opinion the ApplicationArea property should have defaulted to #ALL.

We have a module with many different parts which customers may or may not use. It would be nice to disable them with a click and remove a lot of unused clutter on pages. This system is more software developer controlled opposed to profiles which is more customer based and because it resides in objects it is easy to deploy.

Also I figured out that application area's have a performance advantage. I deliberatly created a very slow performing flowfield and started testing with performance. If the user hides it manually, it is still calculated. If you set the property of the control to Visible=False, the flowfield is also calculated (please Microsoft, tell me why??). However hiding the control because it's application area is not selected, the flow field is NOT calculated.

Perhaps also the rendering complexity is reduced.

In Nav2018 the number of application area's are expanded. Technically it still looks the same.

Sadly Microsoft advises against usage in on premis development. I don't understand, In my opinion it works just fine. https://docs.microsoft.com/en-us/dynamics-nav/applicationarea-property/

Any other thoughts?