This topic explains how to export the spreadsheet template used to import cutom objects of the Dispatch solution to the system and includes details on how to complete the spreadsheet correctly to ensure that no errors occur when importing them.
1. Access the Dispatch solution.
2. In the Export/Import section, click Call Categories, Operating Procedures, ID Types, Call Origins, or Associated Events.
The system displays a screen where objects can be exported and imported.
3. Click Export Template (see figure below).
4. Save the file to your computer and open it.
When the file is opened, the template is displayed in Microsoft Excel. The file includes two worksheets: Instructions, which details how the template should be completed, and a worksheet where the properties and attributes of the objects to be imported can be completed (see figure below).
The tables below explain how each field of the specific worksheets for the objects to be imported must be completed. Fields preceded by an asterisk are required.
• Categories
Field |
Instructions |
ID |
The ID for each category is generated automatically when the spreadsheet is imported to the system. When existing categories are exported for editing, their IDs will be displayed in this field as read-only values. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
* Name |
The name is used to identify the category being created. Enter a value for this attribute by inserting plain text using 1 to 300 characters. |
* Level 1 |
This field is used to identify the first level of the category. This is a read-only field and it cannot be edited. |
* Level 2 |
This field is used to identify the second level of the category. This is a read-only field and it cannot be edited. |
Description |
The description is used to provide additional details on the category. Provide a value for this attribute by entering plain text using 1 to 1,000 characters. |
* Source |
This field is used to indicate the call source of the category being created. This is a read-only field and it cannot be edited. |
Code |
The code makes the category identification easier and works as a keyboard shortcut. Provide a value for this attribute by entering a number. |
Category Attributes |
Any category attributes displayed on the template were previously created and published in the Objects and Attributes section of the Administration module. If the attributes are marked as required in the system, they must be completed for the spreadsheet to be imported.
These fields should be completed according to the type of attribute, as follows: •Attachment: Files cannot be uploaded or deleted through the spreadsheet. However, any files attached through the system will be displayed within brackets separated by semicolons. For example: [file name.pdf];[file name 2.doc].
When creating a category through the spreadsheet, this field will be imported blank, even if it is marked as required. •Date/Time: The format for this type of field is defined when configuring the attribute in the system. If the attribute is registered as "Date", the field should contain only the date; if "Time", the field should contain only the time; and if "Date/time", it may contain either one. If only the date is provided, the time will be 0:00; if only the time is provided, the date will be the date on which the spreadsheet is imported. The date may be in two formats: MM/dd/yyyy or yyyy-MM-dd. The time should be in 24-hour format: HH:mm tt. •E-mail: E-mails should be entered using a maximum of 100 characters in the following format: username@domain.com. •Formula: This is a read-only field, so it is not possible to insert or edit values. These values will be re-calculated once the spreadsheet is imported. •Georeference: Specify a value for this attribute by providing the coordinates in the following format: To define a point: {"type":"Point","coordinates":[-0.09046,51.51095]} To define a set of points: {"type":"LineString","coordinates":[[-0.09046,51.51095],[0,07446,44.51095]]} The coordinates for the points must be entered between brackets, in the following order: "Longitude,Latitude". •Image: Images can only be attached through the system and cannot be added through the spreadsheet. The files attached through the system will be displayed in brackets and separated by a semicolon, for example: "[image.jpeg];[image2.jpeg]".
When creating a category through the spreadsheet, this field will be imported blank, even if it is marked as required. •Link: Links should be entered as: http://www.domain.com or \\server\path. •List of Options: Attributes of this type should be completed with the options available for the attribute, separated by semicolons if more than one value is accepted. •Number: This type of attribute uses the decimal separator (".") and optionally the comma separator (",") to separate thousands. For example, the number 1200 should be filled in as "1,200.00". •Outline: This type of attribute should be completed with the entries using a maximum of 100 characters with each separated by semicolons. For example: Entry 1;Entry 2;Entry 3. •Paragraph: This type of attribute should be completed with normal text. •Relationship: This type of attribute can be single or multiple selection and should be completed with the alphanumeric identifier or the paths of the objects being associated. If more than one object with the same name has been registered in the system, the paths of the objects cannot be used to create relationships and the system will not allow the spreadsheet to be imported. Note that for multiple selection attributes, the paths or identifiers of the objects must be separated by semicolons (";") and no spaces when completing the cells. The identifier of each object should be preceded by "id:" with no spaces after the tag. The identifier is available through the API and can also be found by inserting the name of the object in the general search field and clicking on the corresponding entry, which will then display the identifier at the end of the URL. For business components, the path is specified as follows: business component level > business component type > business component name. For perimeters, the path is specified as follows: parent perimeter name > perimeter name. For assets, the path is specified as follows: parent perimeter name > subperimeter name > asset name. For other objects, simply enter their names. When the spreadsheet is exported, the list of related objects might be truncated if the maximum number of characters allowed in the cell is exceeded. If the cell is not edited, the spreadsheet will be imported and all existing relationships will be kept. To edit the relationships, the ellipses and brackets must first be removed. Note that, in this case, the new relationships will be imported and any previous ones will be deleted. •Text: This type of field should be completed with normal text, respecting any character limits or regular expression masks configured for the attribute in the system.
For details on creating attributes, see Chapter 17: Administration -> Customizations -> Objects and Attributes. |
Author |
This field lists the name and username of the person who registered the category. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Created |
This field lists the date on which the category was registered. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Updated By |
This field lists the name and username of the person who updated the properties of the category. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Updated |
This field lists the date on which the properties of the category were updated. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
• Operating Procedures
Field |
Instructions |
ID |
The ID for each procedure is generated automatically when the spreadsheet is imported to the system. When existing procedures are exported for editing, their IDs will be displayed in this field as read-only values. |
* Name |
The name is used to identify the procedure being created. Enter a value for this attribute by inserting plain text using 1 to 150 characters. |
* Operating Procedure |
This field is used to provide details on the procedure. Specify a value for this attribute by inserting plain text using a maximum of 5,000 characters. The procedure instructions can be divided into items by using line breaks (Alt + Enter) in the cell. The area responsible for executing a particular step and a checkbox can be included so that the service units can indicate which steps of the operating procedure have already been executed. For example, if you enter the text below using the vertical bar to separate the responsible area and the checkbox, the procedure items will be displayed as follows:
1.1 Collect on-site information |checkbox| Police officer 1.2 Return to headquarters |checkbox| 1.3 Call emergency units 1.4 Collect evidence|checkbox| Group A |
* Dispatch Group |
This field is used to indicate the dispatch group responsible for the operating procedure being created. Specify a value for this attribute by entering the name of a group of people previously registered in the Organization module. |
* Call Category |
This field is used to indicate the call category to which the operating procedure is related. Specify a value for this attribute by entering the name of a category previously registered in the Customizations section of this solution. |
Operating Procedure Attributes |
Any operating procedure attributes displayed on the template were previously created and published in the Objects and Attributes section of the Administration module. If the attributes are marked as required in the system, they must be completed for the spreadsheet to be imported.
These fields should be completed according to the type of attribute, as follows: •Attachment: Files cannot be uploaded or deleted through the spreadsheet. However, any files attached through the system will be displayed within brackets separated by semicolons. For example: [file name.pdf];[file name 2.doc].
When creating an operating procedure through the spreadsheet, this field will be imported blank, even if it is marked as required. •Date/Time: The format for this type of field is defined when configuring the attribute in the system. If the attribute is registered as "Date", the field should contain only the date; if "Time", the field should contain only the time; and if "Date/time", it may contain either one. If only the date is provided, the time will be 0:00; if only the time is provided, the date will be the date on which the spreadsheet is imported. The date may be in two formats: MM/dd/yyyy or yyyy-MM-dd. The time should be in 24-hour format: HH:mm tt. •E-mail: E-mails should be entered using a maximum of 100 characters in the following format: username@domain.com. •Formula: This is a read-only field, so it is not possible to insert or edit values. These values will be re-calculated once the spreadsheet is imported. •Georeference: Specify a value for this attribute by providing the coordinates in the following format: To define a point: {"type":"Point","coordinates":[-0.09046,51.51095]} To define a set of points: {"type":"LineString","coordinates":[[-0.09046,51.51095],[0,07446,44.51095]]} The coordinates for the points must be entered between brackets, in the following order: "Longitude,Latitude". •Image: Images can only be attached through the system and cannot be added through the spreadsheet. The files attached through the system will be displayed in brackets and separated by a semicolon, for example: "[image.jpeg];[image2.jpeg]".
When creating an operating procedure through the spreadsheet, this field will be imported blank, even if it is marked as required. •Link: Links should be entered as: http://www.domain.com or \\server\path. •List of Options: Attributes of this type should be completed with the options available for the attribute, separated by semicolons if more than one value is accepted. •Number: This type of attribute uses the decimal separator (".") and optionally the comma separator (",") to separate thousands. For example, the number 1200 should be filled in as "1,200.00". •Outline: This type of attribute should be completed with the entries using a maximum of 100 characters with each separated by semicolons. For example: Entry 1;Entry 2;Entry 3. •Paragraph: This type of attribute should be completed with normal text. •Relationship: This type of attribute can be single or multiple selection and should be completed with the alphanumeric identifier or the paths of the objects being associated. If more than one object with the same name has been registered in the system, the paths of the objects cannot be used to create relationships and the system will not allow the spreadsheet to be imported. Note that for multiple selection attributes, the paths or identifiers of the objects must be separated by semicolons (";") and no spaces when completing the cells. The identifier of each object should be preceded by "id:" with no spaces after the tag. The identifier is available through the API and can also be found by inserting the name of the object in the general search field and clicking on the corresponding entry, which will then display the identifier at the end of the URL. For business components, the path is specified as follows: business component level > business component type > business component name. For perimeters, the path is specified as follows: parent perimeter name > perimeter name. For assets, the path is specified as follows: parent perimeter name > subperimeter name > asset name. For other objects, simply enter their names. When the spreadsheet is exported, the list of related objects might be truncated if the maximum number of characters allowed in the cell is exceeded. If the cell is not edited, the spreadsheet will be imported and all existing relationships will be kept. To edit the relationships, the ellipses and brackets must first be removed. Note that, in this case, the new relationships will be imported and any previous ones will be deleted. •Text: This type of field should be completed with normal text, respecting any character limits or regular expression masks configured for the attribute in the system.
For details on creating attributes, see Chapter 17: Administration -> Customizations -> Objects and Attributes. |
Author |
This field lists the name and username of the person who registered the procedure. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Created |
This field lists the date on which the procedure was registered. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Updated By |
This field lists the name and the username of the person who updated the properties of the procedure. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Updated |
This field lists the date on which the properties of the procedure were updated. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
• ID Types
Field |
Instructions |
ID |
The ID for each ID type is generated automatically when the spreadsheet is imported to the system. When existing ID types are exported for editing, their IDs will be displayed in this field as read-only values. |
* Name |
The name is used to identify the ID type being created. Enter a value for this attribute by inserting plain text using 1 to 50 characters. |
Description |
The description is used to provide additional details on the ID type. Provide a value for this attribute by entering plain text using a maximum of 1,000 characters. |
ID Type Attributes |
Any ID type attributes displayed in the spreadsheet were previously created and published in the Objects and Attributes section of the Administration module. If the attributes are marked as required in the system, they must be completed for the spreadsheet to be imported.
These fields should be completed according to the type of attribute, as follows: •Attachment: Files cannot be uploaded or deleted through the spreadsheet. However, any files attached through the system will be displayed within brackets separated by semicolons. For example: [file name.pdf];[file name 2.doc].
When creating an ID type through the spreadsheet, this field will be imported blank, even if it is marked as required. •Date/Time: The format for this type of field is defined when configuring the attribute in the system. If the attribute is registered as "Date", the field should contain only the date; if "Time", the field should contain only the time; and if "Date/time", it may contain either one. If only the date is provided, the time will be 0:00; if only the time is provided, the date will be the date on which the spreadsheet is imported. The date may be in two formats: MM/dd/yyyy or yyyy-MM-dd. The time should be in 24-hour format: HH:mm tt. •E-mail: E-mails should be entered using a maximum of 100 characters in the following format: username@domain.com. •Formula: This is a read-only field, so it is not possible to insert or edit values. These values will be re-calculated once the spreadsheet is imported. •Georeference: Specify a value for this attribute by providing the coordinates in the following format: To define a point: {"type":"Point","coordinates":[-0.09046,51.51095]} To define a set of points: {"type":"LineString","coordinates":[[-0.09046,51.51095],[0,07446,44.51095]]} The coordinates for the points must be entered between brackets, in the following order: "Longitude,Latitude". •Image: Images can only be attached through the system and cannot be added through the spreadsheet. The files attached through the system will be displayed in brackets and separated by a semicolon, for example: "[image.jpeg];[image2.jpeg]".
When creating an ID type through the spreadsheet, this field will be imported blank, even if it is marked as required. •Link: Links should be entered as: http://www.domain.com or \\server\path. •List of Options: Attributes of this type should be completed with the options available for the attribute, separated by semicolons if more than one value is accepted. •Number: This type of attribute uses the decimal separator (".") and optionally the comma separator (",") to separate thousands. For example, the number 1200 should be filled in as "1,200.00". •Outline: This type of attribute should be completed with the entries using a maximum of 100 characters with each separated by semicolons. For example: Entry 1;Entry 2;Entry 3. •Paragraph: This type of attribute should be completed with normal text. •Relationship: This type of attribute can be single or multiple selection and should be completed with the alphanumeric identifier or the paths of the objects being associated. If more than one object with the same name has been registered in the system, the paths of the objects cannot be used to create relationships and the system will not allow the spreadsheet to be imported. Note that for multiple selection attributes, the paths or identifiers of the objects must be separated by semicolons (";") and no spaces when completing the cells. The identifier of each object should be preceded by "id:" with no spaces after the tag. The identifier is available through the API and can also be found by inserting the name of the object in the general search field and clicking on the corresponding entry, which will then display the identifier at the end of the URL. For business components, the path is specified as follows: business component level > business component type > business component name. For perimeters, the path is specified as follows: parent perimeter name > perimeter name. For assets, the path is specified as follows: parent perimeter name > subperimeter name > asset name. For other objects, simply enter their names. When the spreadsheet is exported, the list of related objects might be truncated if the maximum number of characters allowed in the cell is exceeded. If the cell is not edited, the spreadsheet will be imported and all existing relationships will be kept. To edit the relationships, the ellipses and brackets must first be removed. Note that, in this case, the new relationships will be imported and any previous ones will be deleted. •Text: This type of field should be completed with normal text, respecting any character limits or regular expression masks configured for the attribute in the system.
For details on creating attributes, see Chapter 17: Administration -> Customizations -> Objects and Attributes. |
Author |
This field lists the name and username of the person who registered the ID type. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Created |
This field lists the date on which the ID type was registered. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Updated By |
This field lists the name and username of the person who updated the properties of the ID type. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Updated |
This field lists the date on which the properties of the ID type were updated. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
•Call Origins
Field |
Instructions |
ID |
The ID for each origin is generated automatically when the spreadsheet is imported to the system. When previously registered origins are exported for editing, their IDs are displayed in this field as read-only values. |
* Name |
The name is used to identify the origin being created. Enter a value for this attribute by inserting plain text using 1 to 300 characters. |
* Acronym |
The acronym is used to help identify the origin. Specify a value for this attribute by inserting plain text using a maximum of 10 characters. |
* Description |
The description is used to provide additional details on the origin. Provide a value for this attribute by entering plain text using 1 to 1,000 characters. |
Call Origin Attributes |
Any call origin attributes displayed in the spreadsheet were previously created and published in the Objects and Attributes section of the Administration module. If the attributes are marked as required in the system, they must be completed for the spreadsheet to be imported.
These fields should be completed according to the type of attribute, as follows: •Attachment: Files cannot be uploaded or deleted through the spreadsheet. However, any files attached through the system will be displayed within brackets separated by semicolons. For example: [file name.pdf];[file name 2.doc].
When creating a call origin through the spreadsheet, this field will be imported blank, even if it is marked as required. •Date/Time: The format for this type of field is defined when configuring the attribute in the system. If the attribute is registered as "Date", the field should contain only the date; if "Time", the field should contain only the time; and if "Date/time", it may contain either one. If only the date is provided, the time will be 0:00; if only the time is provided, the date will be the date on which the spreadsheet is imported. The date may be in two formats: MM/dd/yyyy or yyyy-MM-dd. The time should be in 24-hour format: HH:mm tt. •E-mail: E-mails should be entered using a maximum of 100 characters in the following format: username@domain.com. •Formula: This is a read-only field, so it is not possible to insert or edit values. These values will be re-calculated once the spreadsheet is imported. •Georeference: Specify a value for this attribute by providing the coordinates in the following format: To define a point: {"type":"Point","coordinates":[-0.09046,51.51095]} To define a set of points: {"type":"LineString","coordinates":[[-0.09046,51.51095],[0,07446,44.51095]]} The coordinates for the points must be entered between brackets, in the following order: "Longitude,Latitude". •Image: Images can only be attached through the system and cannot be added through the spreadsheet. The files attached through the system will be displayed in brackets and separated by a semicolon, for example: "[image.jpeg];[image2.jpeg]".
When creating a call origin through the spreadsheet, this field will be imported blank, even if it is marked as required. •Link: Links should be entered as: http://www.domain.com or \\server\path. •List of Options: Attributes of this type should be completed with the options available for the attribute, separated by semicolons if more than one value is accepted. •Number: This type of attribute uses the decimal separator (".") and optionally the comma separator (",") to separate thousands. For example, the number 1200 should be filled in as "1,200.00". •Outline: This type of attribute should be completed with the entries using a maximum of 100 characters with each separated by semicolons. For example: Entry 1;Entry 2;Entry 3. •Paragraph: This type of attribute should be completed with normal text. •Relationship: This type of attribute can be single or multiple selection and should be completed with the alphanumeric identifier or the paths of the objects being associated. If more than one object with the same name has been registered in the system, the paths of the objects cannot be used to create relationships and the system will not allow the spreadsheet to be imported. Note that for multiple selection attributes, the paths or identifiers of the objects must be separated by semicolons (";") and no spaces when completing the cells. The identifier of each object should be preceded by "id:" with no spaces after the tag. The identifier is available through the API and can also be found by inserting the name of the object in the general search field and clicking on the corresponding entry, which will then display the identifier at the end of the URL. For business components, the path is specified as follows: business component level > business component type > business component name. For perimeters, the path is specified as follows: parent perimeter name > perimeter name. For assets, the path is specified as follows: parent perimeter name > subperimeter name > asset name. For other objects, simply enter their names. When the spreadsheet is exported, the list of related objects might be truncated if the maximum number of characters allowed in the cell is exceeded. If the cell is not edited, the spreadsheet will be imported and all existing relationships will be kept. To edit the relationships, the ellipses and brackets must first be removed. Note that, in this case, the new relationships will be imported and any previous ones will be deleted. •Text: This type of field should be completed with normal text, respecting any character limits or regular expression masks configured for the attribute in the system.
For details on creating attributes, see Chapter 17: Administration -> Customizations -> Objects and Attributes. |
Author |
This field lists the name and username of the person who registered the origin. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Created |
This field lists the date on which the origin was registered. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Updated By |
This field lists the name and username of the person who updated the properties of the origin. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Updated |
This field lists the date on which the properties of the origin were updated. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
• Associated Events
Field |
Instructions |
ID |
The ID for each associated event is generated automatically when the spreadsheet is imported to the system. When previously registered associated events are exported for editing, their IDs are displayed in this field as read-only values. |
* Title |
The title is used to identify the associated event being created. Enter a value for this attribute by inserting plain text using 1 to 50 characters. |
Description |
The description is used to provide additional details on the associated event. Provide a value for this attribute by entering plain text using 1 to 500 characters. |
Logo
|
This field lists the name and the extension of the file used as a logo for the associated event. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Associated Event Attributes |
Any associated event attributes displayed in the spreadsheet were previously created and published in the Objects and Attributes section of the Administration module. If the attributes are marked as required in the system, they must be completed for the spreadsheet to be imported.
These fields should be completed according to the type of attribute, as follows: •Attachment: Files cannot be uploaded or deleted through the spreadsheet. However, any files attached through the system will be displayed within brackets separated by semicolons. For example: [file name.pdf];[file name 2.doc].
When creating an associated event through the spreadsheet, this field will be imported blank, even if it is marked as required. •Date/Time: The format for this type of field is defined when configuring the attribute in the system. If the attribute is registered as "Date", the field should contain only the date; if "Time", the field should contain only the time; and if "Date/time", it may contain either one. If only the date is provided, the time will be 0:00; if only the time is provided, the date will be the date on which the spreadsheet is imported. The date may be in two formats: MM/dd/yyyy or yyyy-MM-dd. The time should be in 24-hour format: HH:mm tt. •E-mail: E-mails should be entered using a maximum of 100 characters in the following format: username@domain.com. •Formula: This is a read-only field, so it is not possible to insert or edit values. These values will be re-calculated once the spreadsheet is imported. •Georeference: Specify a value for this attribute by providing the coordinates in the following format: To define a point: {"type":"Point","coordinates":[-0.09046,51.51095]} To define a set of points: {"type":"LineString","coordinates":[[-0.09046,51.51095],[0,07446,44.51095]]} The coordinates for the points must be entered between brackets, in the following order: "Longitude,Latitude". •Image: Images can only be attached through the system and cannot be added through the spreadsheet. The files attached through the system will be displayed in brackets and separated by a semicolon, for example: "[image.jpeg];[image2.jpeg]".
When creating an associated event through the spreadsheet, this field will be imported blank, even if it is marked as required. •Link: Links should be entered as: http://www.domain.com or \\server\path. •List of Options: Attributes of this type should be completed with the options available for the attribute, separated by semicolons if more than one value is accepted. •Number: This type of attribute uses the decimal separator (".") and optionally the comma separator (",") to separate thousands. For example, the number 1200 should be filled in as "1,200.00". •Outline: This type of attribute should be completed with the entries using a maximum of 100 characters with each separated by semicolons. For example: Entry 1;Entry 2;Entry 3. •Paragraph: This type of attribute should be completed with normal text. •Relationship: This type of attribute can be single or multiple selection and should be completed with the alphanumeric identifier or the paths of the objects being associated. If more than one object with the same name has been registered in the system, the paths of the objects cannot be used to create relationships and the system will not allow the spreadsheet to be imported. Note that for multiple selection attributes, the paths or identifiers of the objects must be separated by semicolons (";") and no spaces when completing the cells. The identifier of each object should be preceded by "id:" with no spaces after the tag. The identifier is available through the API and can also be found by inserting the name of the object in the general search field and clicking on the corresponding entry, which will then display the identifier at the end of the URL. For business components, the path is specified as follows: business component level > business component type > business component name. For perimeters, the path is specified as follows: parent perimeter name > perimeter name. For assets, the path is specified as follows: parent perimeter name > subperimeter name > asset name. For other objects, simply enter their names. When the spreadsheet is exported, the list of related objects might be truncated if the maximum number of characters allowed in the cell is exceeded. If the cell is not edited, the spreadsheet will be imported and all existing relationships will be kept. To edit the relationships, the ellipses and brackets must first be removed. Note that, in this case, the new relationships will be imported and any previous ones will be deleted. •Text: This type of field should be completed with normal text, respecting any character limits or regular expression masks configured for the attribute in the system.
For details on creating attributes, see Chapter 17: Administration -> Customizations -> Objects and Attributes. |
Author |
This field lists the name and username of the person who registered the event. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Created |
This field lists the date on which the event was registered. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Updated By |
This field lists the name and username of the person who updated the properties of the event. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
Date Updated |
This field lists the date on which the properties of the event were updated. This field should not be completed or edited, and any changes made to it will be ignored by the system. |
5. When finished, save the file to your computer.
Note: For details on importing objects of the Dispatch solution created through the spreadsheet, see Chapter 13: Dispatch -> Export/Import Customizations of the Dispatch Solution -> How to Import Custom Objects of the Dispatch Solution Through a Spreadsheet.