Data Imports: Annotated Spreadsheet Explained - Incident Management

Updated 23 July 2025 20:48

What’s a Data Import?

The Core system data importer uses an Excel file, or a zip folder containing spreadsheets (with attachments). This library data is used to:

Add new objects
Update existing objects
Add new relationships between objects
Delete existing relationships between objects
Assign users to roles in an org
Add attachments to objects.

How is the annotated spreadsheet used?

The data import template is an Excel spreadsheet containing multiple worksheet tabs that you complete with your company’s library data, as part of your implementation journey or evolving daily work. To better enable our customers, we created an annotated spreadsheet to clarify what content belongs to your library data import. This documentation is a handy “side-by-side” resource that details every single field on our annotated spreadsheet. So, if you want a quick reference for those “What goes here again?” moments, we’ve got you covered.

Field Name – what it’s called in the system
Field Description – details field types, functions, and impacts
Field Options – directions for using the fields (like if they’re alphanumeric or drop downs)
Example(s) – sample data to give you extra context
User Tips – expert advice to help get your data import done right!

This spreadsheet’s tab order can’t be re-arranged because it may cause your data import to fail. Some fields are also mandatory for the data import to succeed in Resolver Core. These fields include:

Company
Business Unit
C-Business Unit
Incident Type
Activity Type
Location

Data Import Template – Worksheet tab color coding

Red: MANDATORY – Without this worksheet completed, your data will not upload
Orange: PRIORITY – This is crucial information for effective data
Yellow: OPTIONAL – This information may or may not be relevant to your company
Grey: DEFAULT – Great news! While this information is essential, it is already populated with default values and no work is required

Do NOT hide or delete Rows 1, 2, or 4 on your worksheets (but you are free to change Row 3 for added user instructions).

Library data imports are performed across all our different applications, so your own object types may not populate exactly as what’s detailed on this page. However, many will be the same. Always reference the data import template and app user guide your own consultant has provided.

Icon

Description automatically generated

Wondering how to best use and search this wealth of information? Our pro tip is to open the relevant object type header tab and tap that handy “CTRL+F” keyboard shortcut to find what you need quickly.

Company (Object Type ID)

FIELD NAME	FIELD DESCRIPTION	FIELD OPTIONS	EXAMPLE(S)	USER TIPS
External Ref ID	Default Field: Unique identifier for each Company record. An External Reference ID is an alphanumeric string. It appears in some reports but will not show on the object itself.	Plain Text: No existing External Ref IDs can be changed, but you may continue adding new records with each sheet’s set sequence.	Company1	Can be the same as the company name itself. If importing data from scratch, make up a naming convention. Warning: ensure that the convention is unique in the org to avoid unexpected results!
Name	Mandatory Field: Company name as you would like displayed in the system, used as an anchor for most standard reports.	Plain Text: Limit 300 characters.	Resolver	Company is the highest level of Business Unit hierarchy for company level reporting.
Description	Optional Field: What type of business the company works in.	Plain Text: Multiline.	Our easy-to-use solutions enable the world’s leading organizations to transform Risk Management into Risk Intelligence.	Helpful info but not required on Company worksheet in the system.
Company Status	Default Field: Library workflow state for Company, as populated by the system.	Single Select List	Active	Company will be set as Active for all records.

Business Unit (Object Type ID)

FIELD NAME	FIELD DESCRIPTION	FIELD OPTIONS	EXAMPLE(S)	USER TIPS
External Ref ID	Default Field: Unique identifier for each Business Unit (BU) record. An External Reference ID is an alphanumeric string. It appears in some reports but will not show on the object itself. If more than one BU, you can match the BU name or follow the numeric list format.	Plain Text: No existing External Ref IDs can be changed, but you may continue adding new records with each sheet’s set sequence.	BusinessUnit1 BusinessUnit2	Can be the same as the Business Unit name itself. If importing data from scratch, make up a naming convention. Warning: ensure that the convention is unique in the org to avoid unexpected results!
Name	Mandatory Field: Business Unit name as you would like displayed in the system, used as an anchor for most standard reports. A BU is a segment or subset of the company, often independent in its accounting and operational functionality.	Plain Text: Limit 300 characters.	Information Security	Business Unit name classifies it within the system and will impact your usage of the application.
Description	Optional Field: Details about what the Business Unit does.	Plain Text: Multiline.	Team who identifies and mitigates online/digital organizational threats.	Helpful info when certain BUs are closely related, so you can distinguish between them (e.g., corporate security vs. global security).
ABBREVIATI	Priority Field: Abbreviation or acronym identifying the Business Unit, to quickly create Incidents and help Dispatch teams better understand and address time-sensitive incidents.	Plain Text: Limit 10 characters.	BU1	Use simple language with the “need-to-know” details to address the incident. Can be changed under the “Editing Field” in the Admin side.
INCIDENTIM	Optional Field: Incident Impact Threshold ($) rates your company’s tolerance to specific incidents to show how it may affect your bottom line. This threshold helps the resultant incident response/investigations enable prompt troubleshooting and problem resolution.	Plain Text (numeric): dollar value (without the $ sign) showing the inferred cost of an incident, such as with theft or damaged property.	5000	Number Type – Number. This field may not display in your data import template if Incident Impact Threshold is not currently being tracked by your company.
SUPERVISOR	Mandatory Field: Confirm if the site supervisor must review the incident report. A site supervisor will have specifically assigned access to incidents and their related data visualizations.	Single Select List	Yes No	Search Input. Usually Yes.
TRIAGEROUT	Mandatory Field: The Triage Routing workflow state that determines whether an incident should go to triage for further evaluation (Yes) or immediately open an incident (No).	Single Select List	Yes No	Search Input. If coming from someone outside the incident response team (e.g., HR), most incidents are triaged first, but incident owners can jump right to the open incident state. This status will depend on the Business Units or incident types involved.
RETENTIONY	Mandatory Field: Retention Years, i.e., how long these original incident reports must be kept on file by your company.	Single Select List	1 2 3 4 5 6 7 8 9 10 Do Not Expire	Check your company recordkeeping policies for more information.
Assignable Role: Business Unit Users	Optional Field: Email address of user(s) assigned to specific role(s) in Core.	Plain Text: Can enter multiple emails but they must be comma separated and match the exact case, as capitalizing a user’s first and/or last name will cause errors.	marelaine.rey_2653@coreqe.com, noam.blum_2653@coreqe.com, alex.tucker_2653@coreqe.com	These emails can be entered in Core later by the system administrator. However, if the relevant roles are not entered and assigned in Core, the Data Import will fail.
Business Unit Status	Default Field: Library workflow status for Business Unit, as populated by the system.	Single Select List	Draft Active Archived	Typically set as Active for all records.

Company-Business Unit (Relationship ID)

FIELD NAME	FIELD DESCRIPTION	FIELD OPTIONS	EXAMPLE(S)	USER TIPS
Company OB1 Ext Ref ID	Mandatory Field: Unique identifier for each Company record, as shown in Company’s External Reference ID fields (Sheet 1: Column A). An External Reference ID is an alphanumeric string. It appears in some reports but will not show on the object itself.	Plain Text: Copy and paste this OB1 Ext Ref ID from the Company worksheet tab for all Business Units on this relationship worksheet tab. Related objects are mapped using the external reference IDs assigned to the records on the object type worksheets.	Company1	Note: There will always be one company External Reference ID, as this is static across all its Business Units. Each relationship from a company to a business unit is specified individually (one relationship per Row). Relationships cannot be deleted via Data Import.
Object Name	Mandatory Field: Relevant company name, as shown in Company’s Name fields (Sheet 1: Column B).	Plain Text: Copy and paste the Company’s name from the Company worksheet tab.	Riverdale Industries	Will always be one company name, as this is static across all its Business Units.
*Business Unit* OB2 Ext Ref ID	Mandatory Field: Unique identifier for each Business Unit record, as shown in Business Unit’s External Reference ID fields (Sheet 2: Column A).	Plain Text: Copy and paste this OB2 Ext Ref ID from the Business Unit worksheet tab for all BUs on this relationship worksheet tab. Related objects are mapped using the external reference IDs assigned to the records on the object type worksheets.	BusinessUnit1	Copy all your Business Unit External Reference IDs and names from the second worksheet before completing this C-Business Unit relationship worksheet.
Object Name	Mandatory Field: Relevant company name, as shown in Business Unit’s Name fields (Sheet 2: Column B).	Plain Text: Copy and paste the Business Unit’s name from the Business Unit worksheet tab.	Corporate Shared Services Operations Corporate Security Global Security	Pay attention to the object type name appearing above the column header so that the IDs are copied into the correct columns.