This article describes how to create a mobile app.
You find a simple database schema attached, which will be used for this example and a ready to use shell definition.
The example app is a minimal example about managing the location table in the attached schema.
Navigate to mobile menu in Studio and upload the attached Basic.zip.
Create a new data source and specify the database where you have applied the attached schema.
In the next step we will create a new mobile app which connects a shell and a data source.
If you login into the Apps page with a user which has the role specified above assigned, you should see the mobile app.
If you click on the app you should see a QR code which we need to connect the M.App Enterprise mobile app to your tenant.
NOTE: you only need to do this once per tenant as you can choose between all assigned apps in the app
Download the M.App Enterprise from the app store depending on your platform:
After you installed and launched the app, you can connect to your tenant by clicking on the + button.
Click on the scan QR code button or enter connection details manually.
If you scan the QR code the connection details should be filled in automatically. Click on the save button at the top right.
NOTE: you need a valid SSL certificate or enable HTTP requests in IIS
After you added the server you can select it in the picker and should be able to login with the same username and password as on the Apps page.
On the next page you should see your assigned apps.
If you click the orange button you will see an empty location list where you can add new locations and view existing ones.
In the next article we will examine what is in the Basic.zip and will extend it incrementally.
are you using http or https to connect to the server?
If you are using https, do you have a trusted SSL certificate?
I use HTTPS and the certificate built from M.App Enterprise installation.
we will think about allowing self signed certificates in an upcoming version (accept self signed certificates with a dialog).
In the meantime you can either use a valid SSL certificate (e.g.: Lets Encrypt) or allow http in IIS (Remove localhost in http binding).