Developers can use several data access approaches to consume data from the mobile database.

One of them is to use raw sql queries against the mobile database.

Using raw SQL queries

The developer can create and execute sql statements against the mobile database in order to use the full power of the mobile database engine. Note that the mobile database engine used by default is SqLite. You can consult with the SqLite Documentation about the supported sql syntax.

In order to send queries to the underlying mobile database the developer should use the dataManager “class”:

$ma.dataManager.fetchSql('select id,title from customer order by title',function(customers){
var customersHtml = "";
for(var i in customers){
customersHtml+=customers[i].title
}
$("#customersDisplay").html(customersHtml)
});

This code snippet executes select sql against the mobile database and returns array of objects containing the requested fields as members. Each instance from the customers array will have two members named id and title, because we have mentioned those fields in the select clause. Note that all member values are presented as string data type in this case.

You can also execute insert, update, delete queries against the mobile database like this:

$ma.dataManager.execSql("update customer set title='newtitle' where id=123",function(){alert('executed')});

This code snippet will change the title of the customer with id 123 in the mobile database.

NOTES

  • All $ma.dataManager methods are blocking – the execution of the code is blocked until the operation is completed.
  • You can expect various kind of errors especially , when the code is excuted in the web browser. It is a good practice to provide error callback function

$ma.dataManager.execSql("update customer set title='newtitle' where id=123",function(){
alert("executed successfully")
},
function(error){
$('#errordisplay').html(error).css("color","red");
);

  • String values must be wrapped in single quote char
  • DateTime values must be wrapped in single quote char
  • DateTime values used as part of the sql must be formatted as yyyy-mm-dd hh:MM:ss

//using hardcoded date values
$ma.dataManager.execSql("select * from customer where dateCreated>'2011-12-31',function(){
//using the Date.toSqLiteFormat extended method (recommended)
var dt = new Date();
$ma.dataManager.fetchSql("select * from customer where dateCreated>"+dt.toSqLiteFormat()+"'",function(customers){
//..
});
});

A good practice is to use the LIMIT statement as part of SELECT queries to limit the maximum records.

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: support@dynamcsmobile.com
  • -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.