Dynamics 365 for Field Service Free Sample Questions

Dynamics 365 Field Service Mobile settings provide granular controls for synchronization to manage data usage. The 'Sync on Wi-Fi only' setting for attachments (which are stored as Notes) is a standard feature designed for this exact purpose. This prevents large files from being downloaded over a cellular connection, conserving data. Security roles control access to data, not the sync mechanism. Power Automate is for process automation, not for controlling the mobile client's sync behavior. This is a standard feature, so a custom client is not needed.

The correct process for handling a return from a customer starts with creating a Return Merchandise Authorization (RMA). The RMA record tracks the details of the expected return, including the product, quantity, customer, and price list. Once the physical item is received, an RMA Receipt is created. A Return to Vendor (RTV) is used later if the item needs to be sent back to the original supplier, but the RMA is the initial step with the customer. An Inventory Journal is for internal adjustments, not for processing customer returns.

When using the Dataverse 'When a row is added, modified or deleted' trigger, it is crucial to specify Filtering columns to optimize performance and ensure the flow only runs when necessary. If no columns are specified, the flow might not trigger reliably on all updates or could be throttled. By adding the 'msdyn_substatus' column to the 'Select columns' (previously Filter columns) field, the trigger will fire specifically when that field's value changes, resolving the issue. The trigger condition is a more advanced filtering method and might be empty, but the lack of a specified filtering column is a more fundamental and common error. The connection owner's permissions are for actions within the flow, not the trigger itself. The flow's status must be 'On', but the problem describes a configuration issue.

The Schedule Board settings for the Schedule Assistant include a specific option called 'Default Territory Filter'. Setting this to 'Territory' instructs the assistant to automatically filter available resources to match the territory specified on the Resource Requirement. This provides a soft filter, prioritizing resources within the territory. Modifying the board filter only affects the dispatcher's view, not the assistant's logic. A fulfillment preference is for time-based preferences, and locking the constraint on the requirement is too rigid and must be done manually for each work order.

First, the NTE feature must be globally enabled in the Field Service Settings area. Second, once enabled, the specific NTE amount and transaction details must be entered on the individual Work Order record that requires the NTE.

This statement is true. The automation for converting a product to a customer asset is specifically triggered when the Work Order Product's line status is set to 'Used' and the parent Work Order's system status is 'Open - Completed' or 'Closed - Posted'. This ensures that the asset is only created after the part has been confirmed as installed and used in the service.

Canvas Apps are ideal for creating highly customized, task-specific user interfaces. They can be embedded directly within a model-driven form (like the Bookable Resource Booking form in the Field Service mobile app) to provide a streamlined experience for a specific task like calibration checks. A full model-driven app would be too complex for this simple task. Power BI is for data visualization, not data entry. A custom page is a newer feature but embedding a standard canvas app is the most direct solution for this scenario.

When working offline, all data changes are stored locally on the device. These changes, including the update to the work order product line status which triggers the inventory deduction, are queued for synchronization. The actual update to the backend Dataverse tables and inventory records will only occur once the device regains connectivity and the mobile app successfully syncs the pending changes with the server.

An Inventory Journal is designed for making multiple inventory updates within a single transaction. The administrator can create one Inventory Journal record and then add multiple Inventory Journal Product lines, one for each product, specifying the quantity and warehouse. This is far more efficient than creating individual Inventory Adjustment records. Purchase Orders are for acquiring stock from vendors, and Inventory Transfers are for moving stock between existing warehouses.

To make any entity schedulable, it must first be enabled for scheduling within the Universal Resource Scheduling settings area. This process, often called 'enabling an entity for URS', automatically creates the necessary relationships to the Resource Requirement entity and configures the required booking metadata. Without this step, the system will not recognize the entity as something that can be scheduled.