Dynamics 365: Learn in doing

In MorphX macros are not commonly used. A few places make use of macros such as keeping track of the list of fields stored when using dialogs. It is recommended only to use macros to define constants. Also supports code, but is not recommended as reusing code from macros is not flexible. The main difference between a macro and a method is that a macro has no variable declaration part, and the code in a macro is not validated for errors before executed from a method. This is another reasons for not putting code in macros. When using macros in your code, the macros must be declared after the variable declaration. And the common place to put the definition is in the ClassDeclaration of a class, form or a report. This will make the macro definition available for all parts of the object.   Macro commands: For writing macros a set of simple macro commands are used. Below are few examples. ...

If using more than one company, sometimes, it will be useful to share data from tables with general information, like, tables storing data like zip codes and country codes. The most basic way to share data from a table among all companies is to set the table property SaveDataPerCompany to No. This will merge data for the table and make the data accessible from all companies. In practice, the kernel will delete the system field dataAreaId for the table. Another way to sharing data without having to change any settings in the existing tables is by using Table Collections . A table collection is just a template for tables to be shared by any number of companies and Table collections shared using a virtual company. The form SysDataAreaVirtual is used to define virtual companies. Virtual company is a term used for sharing table collections among a set of companies and does not exist in reality, and therefore, you cannot switch to a virtual company like any normal company. When...

License codes: ·          When purchasing Dynamics Ax you will have to decide on system settings, like, number of users, number of servers, access to MorphX and X++, which application modules you are going to use. ·          For each system setting and module you will receive a license code. All license codes will be compiled in a code letter. These license codes are used for controlling which part of Axapta you will have access to. Only modules with a valid license code will be available in the main menu for end user to use. ·          We can also create our own License codes, However, to use your own license codes you will have to contact Microsoft as they will have to generate license codes on your behalf. Creating new license codes is used by companies creating modules for the GLS layer or by partners who want to sell their own modules. Configuration key...

Base Enums come in handy for categorizing data. One way of categorizing is to create a related table, such as item groups, which is used for grouping inventory items. However, if you only need a fixed number of categories or the application users are not able to define the categories, you can use a base enum, such as Item type, used for defining the type for inventory items. A base enum can have a maximum of 255 entries. A good example for multiple enteries in a base enum is LedgerTransTxt. But in general there will be very few entries. The value of a base enum is stored in the database as an integer value. Entry values starts by default from zero and are consecutively numbered. The property EnumValue will show you the number stored in the database for an entry. We can also manually enter a particular number for an entry in base enum, this can be done if the base enum property UseEnumValues is set to Yes. System enums are located in the AOT ...

·          An extended data type is extended from a base type or another extended data type. The difference is that an extended data type has a property sheet where information such as labels, length and left or right adjustment are stored. ·          EDT are a central part of MorphX. Whether you are adding fields to a table or declaring variables from X++, extended data types should always be used instead of using base types and the reason for that is Dynamics Ax provides powerful features to handle EDTs. ·          The best practice is to check before creating a new extended data type you should check whether in existing one will fulfill your needs. ·          If you have found an EDT which suits your needs, but another label or help text is required, you should create a new EDT with your requirements, but never mod...