Skip to main content

Add a custom app module to the Field Service (Dynamics 365) mobile app

 

After trying Add a custom app module to the Field Service (Dynamics 365) mobile app | Microsoft Docs and failing multiple times, with error message of bad XML, I starter getting curious. 

So here is my solution

  1. Create a solution and include your Model Driven App
  2. Export solution and Extract customization.xml file
  3. Locate the <AppModule> node 
  4. Add the following Xml
<appsettings>
<appsetting uniquename="{name of your App with prefix}_ChannelAvailability">
<value>{name of your App}</value>
<iscustomizable>1</iscustomizable>
<displayname default="App channel availability">
<label description="App channel availability" languagecode="1033" />
</displayname>
<description default="Default Description.">
<label description="Description." languagecode="1033" />
</description>
<settingdefinitionid>
<uniquename>ChannelAvailability</uniquename>
</settingdefinitionid>
</appsetting>
        <appsetting uniquename="{name of your App with prefix}_ServerMode">
<value>false</value>
<iscustomizable>1</iscustomizable>
<displayname default="ServerMode">
<label description="ServerMode" languagecode="1033" />
</displayname>
<description default="Specifies the ServerMode.">
<label description="Specifies the ServerMode." languagecode="1033" />
</description>
<settingdefinitionid>
<uniquename>ServerMode</uniquename>
</settingdefinitionid>
</appsetting>
</appsettings>

Sample:
<appsettings>
<appsetting uniquename="mg_FieldServiceMobileApp_ChannelAvailability">
<value>FieldServiceMobileApp</value>
<iscustomizable>1</iscustomizable>
<displayname default="App channel availability">
<label description="App channel availability" languagecode="1033" />
</displayname>
<description default="Default Description.">
<label description="Description." languagecode="1033" />
</description>
<settingdefinitionid>
<uniquename>ChannelAvailability</uniquename>
</settingdefinitionid>
</appsetting>
<appsetting uniquename="mg_FieldServiceMobileApp_ServerMode">
<value>false</value>
<iscustomizable>1</iscustomizable>
<displayname default="ServerMode">
<label description="ServerMode" languagecode="1033" />
</displayname>
<description default="Specifies the ServerMode.">
<label description="Specifies the ServerMode." languagecode="1033" />
</description>
<settingdefinitionid>
<uniquename>ServerMode</uniquename>
</settingdefinitionid>
</appsetting>
</appsettings>
 

Save the file.
Add the customization.xml file in your zip solution file 
Import it back to your environment.

Comments

Popular posts from this blog

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...

XMLHttpRequest vs Xrm.WebApi

  XMLHttpRequest vs Xrm.WebApi If you have written JavaScript code for Dynamics 365 you have seen the use of XMLHttpRequest or Xrm.WebApi to make server-side calls. The question is which one is the right one to use? So, let’s analyze the two types of calls. XMLHtttpRequest 1.        Synchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", false ); 2.        Asynchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", true ); So, passing true parameter is going to make asynchronous call while passing it false is going to make a Synchronous call. Xrm.WebApi 1.        Asynchronous a.        There is...