Mobile EAM

8. Optimization and Performance

Deployment Best Practices

All about the data quality

Make sure your D365F&O database is free of DB sync errors. It's helpful to use full sync and complete build between major releases.

No mismatches

Make sure you don't have any mismatches between your Dynamics 365 F&O environment's versions.
Make sure you have the same release version for Dynaway products. Dynamics 365 FO models and Mobile Apps in the same major release.

How to deploy

Dynamics 365 F&O can be updated via lcs.dynamics.com (all-in-one package) or a Microsoft DevOps pipeline (version control).
Microsoft LCS Deployment manual
Microsoft Azure DevOps Deployment

Mobility Optimization Guide

Mobile application performance and data consumption are directly impacted by the number of active users and the volume of work orders. Below are a set of guidelines outlined for you to follow to maintain a high-performing and efficient system. These practices will help you optimize mobile operations and ensure consistent system responsiveness.

  1. Entity setup
    • Path: Mobility > Setup > Entity setup.
    • Disable unused entities to avoid syncing unnecessary data.
    • Shorten the date range for data storage.
  2. Entity initialization
    • Path: Mobility > Periodic > Entity initialization.
    • Run only after each Dynamics 365 and Dynaway update. It prevents corrupted or incompatible data and updates entity structure to match the latest version.
    • This process ensures mobile data is correctly aligned with format changes (e.g., new fields added in a new release).
  3. Mobile framework cleanup jobs
    • Path: Mobility > Periodic > Mobile framework cleanup jobs.
    • Schedule this as a daily recurring batch job to ensure a good performance:
    • Clean temporary paging table
      • Deletes data in the temporary paging table older than retention days set up in the database
    • Clean client and handler logs
      • Deletes handler logs which are older than handler log retention days from dialog
    • Clean up modified entities
      • Deletes mobile entity data not needed
      • Depersonates mobile entities for work orders and maintenance requests
  4. Handler logs
    • Path: Mobility > Setup > Handler setup.
    • Handlers are endpoints in F&O used by the mobile app to send or receive data.
    • The mobile client must be online to invoke a handler.
    • It is best practice to disable handler logging by default. Enable only when troubleshooting. Excessive handler logging can negatively impact system performance, especially with many concurrent users.
    • Use the Handler overview to:
      • Monitor active handlers and log volume.
      • Open detailed logs when diagnosing issues.
      • Activate the webSynchronizationGetter handler to measure sync processing time in milliseconds.
      • Poor D365 performance will directly impact mobile execution speed.
  5. Synchronization frequency
    • Path: Mobility > Setup > Module configuration > General > Synchronization > Synchronization frequency.
    • Set frequency to every 10 minutes.
    • This interval is sufficient because data also syncs when:
      • A page is refreshed.
      • A work order is scheduled.
      • Mobile data is sent to F&O.
  6. Cached saved search lists
    • Path: Mobility > Periodic > Cache saved search lists.
    • Caching saved search lists is supported and can improve the offline experience, but excessive caching can negatively impact mobile performance. Use it strategically based on user needs.
    • When a user is assigned a saved search list (e.g., Work orders, Requests, or Objects), they can view the included entities while online. Any entity the user opens will remain available on their device for offline access.
    • If you want users to access all entities in a list offline, even those they haven’t opened, then you can mark the list as Cached. When a list is cached, the mobile client will automatically download all associated entities. This improves offline usability and speeds up loading times.
    • However, it’s important to use caching selectively. By default, few entities are marked for prefetching to preserve mobile performance. Caching many saved search lists or large numbers of entities can:
      • Increase the time it takes for the mobile app to start after a data initialization.
      • Slow down the app when new objects are personated in F&O.
  7. Caching for document types
    • You can enable offline caching of documents used in the mobile app.
    • However, downloading all documents in advance may affect app startup time and data usage.
    • Recommended only when offline access to documentation is critical.
  8. Image quality impact on performance
    • If an object images appear to be lower quality on the mobile app compared to the original files, it's due to image compression. To reduce data usage and improve performance, images are automatically resized and compressed before being sent to the mobile device.
      • You can adjust image handling behaviour through the following settings. These settings allow you to define compression thresholds and control when compressed or smaller image versions are used.
    • Mobile parameter setup > Object image compression threshold.
      • Defines when images should be compressed.
      • Example: Threshold set to 3 MB. Large images above the threshold are automatically compressed to reduce sync time and load.
    • Mobile configuration
      • Max image attachment upload size: Default: 200 KB (If images sent from mobile to F&O are blurry, increase this limit)

0. Dynaway optimization tools
0. Dynaway optimization tools
1. Entity setup.
1. Entity setup.
2. Entity initialization batch job
2. Entity initialization batch job
3. Mobility framework cleanup jobs.
3. Mobility framework cleanup jobs.
4. Handler logs cleanup
4. Handler logs cleanup
5. Dynaway Overview file.
5. Dynaway Overview file.

Inspect Entities

To inspect entities, go to Mobility > Inquiries > Inspect entities.

This functionality (available in Dynaway 2307 update) is useful when an error occurs during the transfer/synchronization of a given entity. You can find all errors on the 'Failed entity submits' form.

On the 'Entity setup' form related to failed entity submits, there is a column on the grid that shows how many times a problem occurred with data transfer for a given entity.

When clicked, a button in the top menu Failed entity submits opens the 'Failed entity submits' form.
With a filter, i.e. shows only errors for the entity previously selected on the 'Entity setup' form.

  • Inspect for Selected Entity
  • Failed Entity Submits

Inspect for Selected Entity

Users can now inspect a selected entity from entity setup (Setup > Entity setup).

Failed Entity Submits

  • The number of failed entity submits for an entity is added to the grid overview.
  • Failed entity submits can be opened from the overview. No multiselection.

1. Entity Inspector.
1. Entity Inspector.

Copyright Dynaway A/S

Privacy Policy