How to populate field values from any Source table (Incident, Case, Asset, Location etc.) to Work Order table field How to populate field values from any Source table (Incident, Case, Asset, Location etc.) to Work Order table field Introduction: ServiceNow maintenance module is very flexible and allows to create maintenance schedules for location (site inspection), CI/Assets/Install base (device maintenance) etc.. Key information related to to-be-maintained entities may be relevant and essential information for field service personas (Dispatcher, Technician), to take informed decisions. This article aims to guide readers through the process of linking fields from source table to Work Order. We shall take the example of a source table, Location (cmn_location) and link the location and priority values from Locations to Work Order table Step 1: Create a Maintenance Plan To initiate the process, create a maintenance plan within the "cmn_location" table. This plan should outline the details of the maintenance tasks to be performed, including the frequency and scope of inspections. Step 2: Configure Regular Maintenance Schedule Next, configure a regular maintenance schedule for the plan. This schedule should specify the frequency of inspections, such as daily, weekly, or monthly, depending on the maintenance requirements. Step 3: Associate a Template to the Schedule Associate a template, such as "Fiber line inspection," to the maintenance schedule. This template will serve as a blueprint for the tasks to be generated when the maintenance is due. Schedule and associated template Example : Location records under maintenance : How to link source table fields to Work Order fields : Here, the example is to carry forward the location, priority fields. Install "Template management for field service" plugin (ID : com.snc.fsm_template_management) Step 1: (Create Table mapping) Navigate to Field service -> Template management -> Table mapping Click on NEW button and create the following Configuration Step 2: (Create Field mapping) From the above Configuration related list - "Basic field mapping", Click on New Button. And fill in the form with something like shown below: Step 3: (Create Attribute mapping) Navigate to Field service -> Template management -> Attribute mapping Click on NEW button and create the following Configuration Here we are linking the "template" we associated to schedule in our example with the "table map" we just created. This implies that, whenever a work order is generated from the given "template" where there is a table map associated, and the work order is generated from the "table map" - "source table" , All the field mappings done to the table map, will be applied. i.e., the data will be carry forwarded from the source fields to the target table fields seamlessly. Output : Work orders generated with configured data i.e., Priority and Location fields are populated as configured in the table, field mappings. Conclusion: The above is an example for carry forwarding fields from source entity to work order entity. This is a generic solution and can be used for any source table.