It Seems that Microsoft Dynamics team is bang on their target and managed to stick to NAV product Roadmap released earlier –

Congrats to Microsoft Dynamics Team for their great work.
Its Really Fun to Work with Microsoft Dynamics Nav / D365 Business Central
One of my student asked the following question few days back and I just tried to answer them in simple language. You may already know those answer right.
“can u please tell me the diff. in quit/break/skip/exit in NAV & how to use it properly……..”
Just to answer your question –
1. Quit
Quit can only be used in Report, Dataport or XMLport. (Like Currreport.quit). It quits (come out from) the report or dataport or XMLPORT. If some processing of data happened before the quit statement, all of those data manipulations will be reversed (rolled back).
2. Break
Break can be used in 2 places –
a. in any loop (repeat..until) – This statement will break the loop and come out of the loop without further processing. All the data manipulation before this statement will remain intact.
b. In a report or dataport or XMLport. This statement will take you out from any trigger (like on prereport, Onpresection etc)
3. SKIP
SKIP is only used in Report / Dataport / XMLPORT. This statement skips the iteration of a dataitem.
4. EXIT
EXIT normally used in functions / triggers to return a value. (say a function returns a numeric value –
Myfunction(integer A, Integer B) Integer—
EXIT(A+B);
————————————————-
Hope the above answer helps you. I will try to send a more detailed answer to you (with example) soon. Keep writing me your problems and ask ur freinds to send their problems to me too.
You can also send me a mail to snehanshu.mandal@gmail.com
Simple use the same Power function – And just change the ‘Power’ parameter of the function.
So to find out the square root of say 16, use
Power(16,1/2); This will result in 4
to find out the Cube root of say 8, use
Power(16,1/3); This will result in 2.
to find out the nth root of any number just use –
NewNumber := Power(Number,1/n);
2. Use the functions available in Codeunit 400 (SMTP Mail) :
You may argue – Why not? I am selecting all the accounts from Chart of accounts and making a dimension mandatory for them. And it works.
But think again. Think about a situation where you are creating a new account in Chart of Account.
The dimension you made mandatory for rest of the accounts will not be readily become mandatory for this new account.
So you have to make that dimension mandatory for this new account manually following the same method. If you forget, it can be a disaster waiting for you.
Rather the right method of making a dimension mandatory across all the accounts is much simpler and full proof (foolproof as well). Use the ‘Account type default Dim.’ feature. Its available in the Dimension window itself.
To understand the concept you need to go back to history of Navision and also need to understand the basic concept of Dimension. Let me try to elaborate it.
Dimension: Dimensions are nothing but parameter for your analysis of data. In other words, they are additional information attached to your transactions and you can analyse / summarize your transactions on the basis of those parameters. Say, you want to analyse your fuel expenses on the basis of Car no. So you need to define a dimension called ‘Car’ and put all the car nos in the dimension value list.
Similarly, if you need to analyse telephone expenses on the basis of Telephone nos or travel expenses on the basis of employee nos then, you will define Telephone and Employee Dimensions and list down the dimension values for those dimensions. So at the end you can have a list of dimensions & their values as below:
— Car — 1001 — WB 300356
— 1002 — UP5005333
— 1003 — DEL678932
This way you can define any no of dimensions and attach any no of dimension values while entering any transaction in the system.
Now that’s was Dimension. So what is global dimension? Lets go back few years down to Navision history.
There was time when Navision didn’t have the facility to attach unlimited no of dimensions to transactions. Instead it had only 2 fixed dimensions with each transactions – Department & Project. And to attach these 2 dimension with each transactions, Navision had created these 2 fields in all the transaction tables (e.g in 81 – Gen. Journal Line, 36 – Sales Header, 37 – Sales Lines, 38 – Purchase Header, 39 – Purchase Header and so on). See the figure below.
Say you want to generate different invoice nos based on to where (geography) you are selling your service / material. So your domestic sales can have invoice nos which is different from invoice nos of export sales.
Now to implement the above feature, you need to use at least 2 no. series for invoice numbering? But in Sales & Receivables Setup’s Numbering tab, you have provision of mentioning only one no. series for Sales Invoice nos. how to resolve this?
Can we disable the F4 function button in Navision?
Few years back, I had a situation in one of my implementation, where users used to delete the sales order inadvertently by pressing F4 (Their intention was to create a new order by pressing F3).
Now how to stop it. I had solved it in a very simple way by creating a new dummy menu item in one of the menu button present in the order window and assigning F4 as the shortcut key to that menu item. It just overridden the default F4 functionality (delete function). Here is how i did it –
Chart of account is a window where your list of accounts is displayed. The same window is used to create a new account as well as finding a particular account (you are looking for analysing it).
You would have been amazed knowing some of the properties which you use quite regularly but never bothered about knowing them. In this series of posts, we will try to under few of them. Today we will start with ‘AutoCalcField‘
You all know that if you display a flow field onto a form or a report, the system calculates the flow field value automatically and displays it. Do you know why system behaves like this? Just because of the property ‘AutoCalcField‘.
This simple property is related to any control onto a form or a report which displays a flow field. In other words, you can change this property in those controls whose source expression is a flow field.
Why we don’t really notice them? Because ‘Yes’ is the default value for this property. If you turn it to ‘No’, the control simply will not calculate the flow field value automatically.
To check it out, open the Vendor card (form 26) in design mode and go to the property of the field “Balance (LCY)”. You will find, the AutoCalcField property is set to ‘TRUE’ by default. You can change it to ‘No’ and see whether this field is anymore displaying the Vendor Balances or not.
Good Luck.
See you in Next property 🙂