Tip: You can use filters for better results
-
Latest News
-
Quick Start
-
Work Place
-
-
- How to schedule tickets
- How to search for tickets
- How to query tickets
- How to filter for tickets
- How to use the Ticket Clipboard tab
- How to grab/ungrab tickets
- How to link & unlink components together
- How to download ticket data as a excel sheet
- How to copy filters/queries for colleagues
- How to email filters/queries to colleagues
- How to assign/unassign tickets to/from partners
- How to manage parts
- How to show tickets on Map
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer
- How to schedule tickets
- How to publish/unpublish tickets
- How to lock/unlock tickets
- How to lock/unlock engineers
- How to manually reschedule PUDOs
- How to show tickets on Map
- How to manage availabilities
- How to manage subgroups
- How to display an additional time zone
- How to move tickets back to the Ticket Pool
-
-
-
- How to manage parts
- How to assign/unassign tickets to/from partners
- How to use the Interaction buttons
- How to use the Workflow buttons
- How to use communications
- How to schedule tickets
- How to edit ticket details
- How to cancel a ticket
- How to use the Remove Pending button
- How to report a ticket
- How to create intervention infos
- How to create intervention reports
- How to cancel an appointment
- How to clone tickets
- How to edit private notes
- How to add & remove skills
-
Admin Panel
-
- How to connect with ServiceNow
- How to create test tickets
- What are aliases?
- What does workflow mean?
- What are appearances in context of workflows?
- What are buttons in context of workflows?
- What are automations in context of workflows?
- What are guides in context of workflows?
- What are actions in context of workflows?
-
- What is the Process menu?
- What does workflow mean?
- What are appearances in context of workflows?
- What are buttons in context of workflows?
- What are automations in context of workflows?
- What are guides in context of workflows?
- What are actions in context of workflows?
- How to create & edit projects
- How to create & edit custom forms
- How to create & edit lists
- How to customize the Customer Portal
- How to create & edit automated actions
- How to create & edit conditions
- How to create & edit indications
- How to set up email templates
- How to create & edit ticket durations
- How to create & edit custom fields
- How to create & edit value sets
- How to create & edit SLA Profiles
- How to repair tickets with Ticket Workflow Monitoring
-
Fieldcode FMA app
-
- Fieldcode FMA app
- How to download the Fieldcode FMA app
- How to login
- How to configure multiple accounts
- How to enable/disable notifications
- How to change the theme
- How to log work times
- How to synchronize tickets
- How to navigate to appointments
- How to log drive times & drive breaks
- How to inform dispatchers
- How to view archived appointments
-
-
Customer Portal
How to import tickets
If you want to import tickets from another system you can use the ticket import.
The tool gives you the option to import excel sheets with Ticket data into the Fieldcode Work Place with the right standards.
Go to sidebar -> Ticket import button
The import is clustered into five steps:
1. Upload -> 2. Configuration -> 3. Test -> 4. Import -> 5. Done
Excel template for ticket import
You don’t want to prepare your .xls file for yourself?
No problem, just use our template and replace it with your ticket data!
1. Upload
- Select the Project Name you want to assign your Excel File to via the dropdown.
- Select the Configuration you want to use with your Excel File to via the dropdown.
- Click Add File and select the Excel File you want to import with File explorer OR drag it directly from your desktop to the Drag & Drop window.
Please wait until the file is added. - Click NEXT to proceed to the next step.
The excel file must begin on sheet 1 and header A1.
Please also ensure that you stick to the format specifications in order to make the ticket import as smooth as possible:
- The LSDT date must be formatted in this scheme: YYYY/MM/DD
- The system uses the GMT timezone, therefore please make sure to convert the LSDT date and time fields accordingly in your template first
- The preferred appointment time must be formatted in this scheme: YYYY/MM/DD
- YYYY/DD/MM formatting will cause failed validation
- Only .xlsx and .xls files are accepted by the ticket importer
2. Configuration
You have the following options in this menu:
Switch your Excel Fields, Adjust to Fieldcode Ticket Fields, Edit Values, Allow Duplicates and / or advanced options.
- Switch Excel fields: Mandatory fields are necessary for system to process. By clicking the drop down in one of these fields you can chose another field that should be mapped to Fieldcode Ticket Fields.
- Adjust to Fieldcode ticket fields: The system tries to also adjust additional fields to Fieldcode Mapping and suggests appropriate fields. However, they can also be further mapped manually by clicking the drop-down.
- Edit Values: By clicking the button inside a field you can change the assigned value (subcategory, category, or boolean) of your field.
- Allow duplicates: This toggle decides if the remaining fields that contain the same data are further allowed to be kept in the import process or should be kicked out. The default setting is Duplicates allowed.
- Advanced options: When the context menu is chosen, you can see three dots beside every row which enable further functionality. In the context menu, you have the options to Add fixed values, Add Prefix, and Add Suffix to the selected Ticket field. Click Save after you are making changes here, otherwise, changes won’t be saved.
You can click on the preview to check if you are satisfied with your mapping.
After that click on Test configuration to proceed to the next step.
3. Test
The importer now runs through automatically and validates your field mappings. The validation can either fail or succeed.
Test failed
In case the test failed you will be prompted with the errors and the affected tickets and can go back to configuration or Skip & Start import (not recommended!).
Test succeeded
In case of success, you can click on Start import to start the next step.
4. Import
The Import will now run through automatically while showing the number of tickets that are being processed.
5. Done
The import can either run through successfully as above or with skipped tickets as below.
Regardless of how the Import ends you have two options now.
Either click DONE to finish the process or press click here (as shown in the screenshot above) to save the configuration for later purposes.
If you click on click here you have to do the following to save your configuration:
- Insert a name for your configuration.
- Insert a description for your configuration.
- Click on Save.
0 out of 5 stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |