The developer can organize frequently used pieces of code into separate Code files.

The Code files are accessible from the Code link on the left of Dynamics Mobile Studio. The code section is useful when you want to create a code (function) to share between views and other code areas of the module.


The developer can:

  • Add new Code file by clicking the New Code Resource button on top
  • Delete existing Code file by checking the checkbox next to the Code file and clicking the Delete button
  • Opening the Code file properties by clicking the (i) icon

Adding and writing Code files

The developer can add a new Code file by clicking the Add Code button on top. It will allow the developer to enter the name of the Code file and save it. The developer has to find the new Code file in the list and click over the title to open it. It will navigate to the Code file editor.

The developer can:

  • write the code into the Code file editor and save the changes by clicking the [disk] icon on top
  • click the [pencil] icon to open the Code file prpoperties
  • search within the Code file editor by pressing CTRL+F from the keyboard
  • click the [search] icon to open the global search window and search text within all module’s components.

Note that all Code files are combined into a single javascript file during code generation and delivered to the device/browser. The developer has to decide the actual “namespace” where the code will be nested. The functions defined in the Code files are placed into the global “namespace” by default.
The developer can use $ma namespace to access resources from the Mobile API.

Use the Code files to:

  • implement a set of functions/methods to use into the Views
  • extend the existing business objects by introducing new members/methods(functions)

For example let’s assume we have a defined business object with name SalesDocumentLine. We can add new methods(functions) like this:


We have two new methods added – calculate() and clear().

We can use the methods in the following way:

var line = new $;

Renaming a Code file

The developer can rename the code file by clicking over the [pencil] icon to open the properties window. The properties window will let the developer to enter the new name and save the change by clicking the Save button.

Note that the name of the Code file is not used runtime. It is only meaningful for the developer.

Last Updated: Dec 1, 2015

We provide public releases of our products once a year or more and commit to 12 months support for all public releases. We also provide releases to support the new versions of Microsoft Dynamics NAV and Microsoft Dynamics AX within 12 months after a new version of the ERP is released.

We envision the support as a major component of our effort to provide our customers with mission critical software solutions. We provide support services to customers in order to guarantee their business continuity. Our customer shall report issues or other cases, which requires support. The reporting is performed by authorized personnel from the Customer’s side via the standard support channels described below.

The support is provided in order to:

  • Solve current problems reported by authorized representatives of the Customer on occasion and in connection with Dynamics Mobile
  • Diagnose problems in connection with the standard system functionality
  • Diagnose problems in connection with the functionality customized by Dynamics Mobile team
  • Analyze and eliminate of any “defect” – a mistake in the program code of functionality, whcih affects the Client’s operations

The support services are only provided in response to a support request submitted by authorized personnel from the Customer’s side via any of the support channels:

  • -e-mail:
  • -phone: 00359 2 817 33 63

We provide different response times to support requests based on the request priority as follows:

Priority Reaction time Description
Critical to 2 hour Causes business process block.
Medium up to 8 hours Affects the business process as there are no work around actions.
Low up to 2 business days Low impact issues and requests, which does not affect the system.