The views (mobile screens) may pass information to each other. The concept is called Task Context.

The Dynamics Mobile Studio provides the concept for tasks steps and views- see the User Interface section for more information.

Each user activity is developed like a task, which contains a set of steps. The user navigates between the steps. Each step is associated with a view ( form ) displayed on the device’s screen.

Sometimes the developer will need to pass data between the steps/views and store data, which must be available during the execution of the task.

Dynamics Mobile provides special API for this purpose:


  • The context object serves like a local (device memory) temporary storage for data
  • The context object stores and extracts data by using unique keys – similar to a dictionary/hashtable
  • The context object can only be used to pass data between steps/views within a single task
  • The context is cleared before a task is launched by the user – can NOT be used to pass data between tasks
  • Do not abuse the context object – avoid placing large objects like arrays of business objects and others because the context actually performs JSON serialization/deserialziation, which costs CPU cycles.
  • The data within the context object will survive a web browser page refresh.

Let’s assume we have two views: View1 and View2 and that we have a task, where View1 is displayed first and then View2 is displayed. We want to pass some data from View1 to View2.

Let’s place some data into the context from View1:

// fetches a customer from the database
alert('context set')
}); //placing the customer object into the context

The data can be placed in the context object by using the $ma.uiManager.context.set(key,data) method. The customer business object is placed inside the context and ready for consuming in this case.

Let’s get some data from the context from View2:

throw 'Strange, but customer is not in the context!';
$ma.uiManager.alert('The customer is there!');

The data can be retrieved by using the $ma.uiManager.context.get(key,defaultValue,success,failure) method. The get method will return the value supplied in the defaultValue parameter if no data exists under the given key. There is a second overload of the get method:


The developer can supply a default value, which will be returned if the context does not contain the requested key.

$ma.uiManager.context.get('mycustomer',new $,function(customer){
$ma.uiManager.alert('The customer object will always be there!');

The developer can also use $ma.uiManager.context.remove(key) method to remove data from the context.


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.