February 09, 2018

Mobile app development in D365 for FO- Part II

Hi Folks,

In my last post, Mobile app development in D365 for FO - Part I, we discussed how to create a simple workspace for the mobile platform. In today's post, I will share some of the deployment methods for mobile workspace.

In the current version of the mobile app, we can create two types of workspaces that are available to deployment.

a. In database
b. In metadata

a. Database workspaces:
When a user builds an app workspace using web API, it will have stored in the database and anyone can edit or delete such pages.

Database pages easy to create with navigation only. Mobile app framework will record user action and convert into logic, pages actually work the same as a user will record for it. It’s important that the user has clear visibility of what user requirements before creating a page or action.
There are three sections in mobile workspace

i. Pages: Pages that will appear in the mobile workspace, to display data.
ii. Action: To perform CRUD operations.
iii. Logic: Attach the JS file.

Current mobile app framework is flexible in terms of designing flow, the user must be very careful how the user is recording the business process while configuration.

b. Metadata workspace

These pages need to be developed using classes in VS. Metadata workspaces cannot be created directly in VS, firstly user needs to create a workspace in user database using the above method and then attached user workspace to it.


-Harry Follow us on Facebook to keep in rhythm with us. @theaxapta

November 23, 2017

How to Delete a model in Dynamics 365 for FO


I was trying for this for very long time, on initial stage of development it was one of the biggest headache for me. HOW TO DELTE A MODEL. So now finally I come to conclusion on this.

Note: I would recommend check with all other developer who is sharing the same dev machine before deleting this to make nothing will go wrong. Take a backup of your code.

Prerequisite:
1.     Login to server using admin credentials
2.     Check your model directory it must be sore under below path/folder
C:\AOSService\PackagesLocalDirectory/<your model>





There can be two scenarios here,
1.     Model belongs to its own package
2.     Model belongs to standard (existing) package.

1.     If your model belongs to its own package (For example: An extension package with no other models in the package):
a.      Stop the following services: The AOS web service and the Batch Management Service
b.     Delete the package folder C:\AOSService\PackagesLocalDirectory\<your model>
c.      Restart the services from step 1
d.     If Visual Studio is running, refresh your models (Visual Studio > Dynamics 365 > Model management > Refresh models)
e.      In Visual Studio, perform a full database synchronization (Visual Studio > Dynamics 365 > Synchronize database...)





2.     If your model belongs to a package with multiple models (For example, <your model> overlays Application Suite):
a.      Stop the following services: The AOS web service and the Batch Management Service
b.     Delete the model folder C:\AOSService\PackagesLocalDirectory<PackageName>\<your model> (In this example PackageName=ApplicationSuite)
c.      Restart the services from step 1
d.     In Visual Studio, refresh your models (Visual Studio > Dynamics 365 > Model management > Refresh models)
e.      In Visual Studio, build the package that the deleted models belonged to (Visual Studio > Dynamics 365 > Build models...)
f.       In Visual Studio, perform a full database synchronization (Visual Studio > Dynamics 365 > Synchronize database...)


Enjoy..
Harry.

Disc: This post is referred from here.