Tip: Start typing in the input box for immediate search results.
-
Quick Start
-
- What is Fieldcode?
- Definitions
- What are tickets, projects and workflows?
- How to log in to Fieldcode
- What is the Fieldcode Support Panel?
- What are components?
- What are views?
- Ticket statuses and their meaning
- Ticket colors and their meaning
- Map symbols and their meaning
- Frequently Asked Questions
- Setting up Fieldcode
-
-
Release Notes
-
Short Overview
-
Fieldcode Work Place
-
-
- How to schedule tickets
- How to search for tickets
- How to expert-search for tickets
- How to filter for tickets
- 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 partners
- How to manage spare parts
- How to show tickets on Map
- How to use the Clipboard
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer in the Timeline
- How to schedule tickets
- How to publish tickets to engineers from the Timeline
- How to lock/unlock tickets
- 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 use the Interaction buttons
- How to assign/unassign tickets to partners
- How to manage spare parts
- How to use the Workflow buttons
- How to use the Ticket info button
- How to use the Email button
- How to use the Comment button
- How to schedule tickets
- How to use the Remove Pending button
- How to cancel a ticket
-
Fieldcode Admin Panel
-
- What is the Process menu?
- What is the Workflows menu?
- How to create & edit projects
- Automated Actions in the overview
- How to setup custom Automated Actions
- How to setup pre-configured 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 custom forms
- How to create & edit value sets
- How to create & edit SLA Profiles
- How to move stuck tickets via Ticket Workflow Monitoring
-
- Articles coming soon
-
Fieldcode Mobile App
-
Fieldcode 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
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 fill it in with the necessary 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 LSDT date must be formatted in this scheme: YYYY/MM/DD
The preferred appointment time must be formatted in this scheme: YYYY/MM/DD
YYYY/DD/MM may cause failed validation.
Only .xlsx and .xls files are accepted by the 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.