Issue Description: 

Importing the Model Driven App “Field Service” from DEV to UAT. Recently the importing is getting failed with an error message: “Import of app module(s) failed: Entity ‘appsetting’ With Id = xxxxxxxxxxxxxxxxxxxxxx Does Not Exist”.

 

Analysis by Microsoft: 

Microsoft have confirmed that when importing some entities such as Marketing List, SystemUser, Team, CustomerAddress, Position, TransactionCurrency entity this error can occur

Solution “XXXXXX” failed to import: ImportAsHolding failed with exception :Import of app module(s) failed: The evaluation of the current component(name=AppSetting, id=xxxxxxxxxxxxxxxxx) in the current operation (Update) failed during managed property evaluation of condition: Managed Property Name: iscustomizableanddeletable; Component Name: AppSetting; Attribute Name: iscustomizable;  

 

Solution (Temporary Fix):

Microsoft product group had requested to remove the following section (AsyncOnLoad) from the Customization.xml file:

 

 

Save the Customization.xml then zip all the solution files and then import it into the target environment to see it successfully importing without any appsetting id errors.

 

Microsoft Product Group confirmed the following:

This is an existing bug with the Field Service – Model Driven App. The bug fix will be prioritized based on the existing backlog and release cycle. As the bug was recently reported, there is no estimated completion time yet. However, the product group has confirmed that it should be resolved within the next six months. You can track the progress of the bug by referencing the bug number (5083419) when necessary.