Wiki source code of Export objects
Last modified by Андрей Калиновский on 2023/04/26 11:26
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
7.1 | 1 | (% class="wikigeneratedid" id="H42D43A44143F43E440442" %) |
| 2 | ((( | ||
| |
9.1 | 3 | Export window: Object selection is invoked by pressing the button in the Export column, in the Objects line. |
| |
6.1 | 4 | |
| |
15.1 | 5 | == Export: Select object == |
| |
6.1 | 6 | |
| |
9.1 | 7 | Options: **Export destination** , **Search** , list of objects |
| 8 | At this stage, select the export destination and the objects that we want to export. | ||
| |
6.1 | 9 | |
| |
15.1 | 10 | [[image:image-20230425154324-1.png]] |
| |
6.1 | 11 | |
| |
9.1 | 12 | **Destination of export** - a field, when clicked, a list of two options drops out: **File** and **Element** |
| |
6.1 | 13 | |
| |
9.1 | 14 | **File** - in the last step, the data will be exported to a file and downloaded to the user's computer. |
| 15 | **Element** - in the last step, the data will be exported to an existing element in the system, that is, the last import step will be used Import **: Import Destination** . | ||
| |
6.1 | 16 | |
| |
9.1 | 17 | **Search** - it is possible to search for objects from the list in the string. A search is performed by Object, Model and IMEI. |
| |
6.1 | 18 | |
| |
9.1 | 19 | If one object or none is selected, **the Export Destination** can be either **File** or **Item** . |
| 20 | If two or more objects are selected, **the Export Destination** is set to **File** . The field is blocked until the number of selected elements becomes one or none. | ||
| |
6.1 | 21 | |
| |
15.1 | 22 | == Export: Select object properties == |
| |
6.1 | 23 | |
| |
9.1 | 24 | In this window, you select the exported elements of the object. Depending on the number of previously selected objects and the destination of the export, the appearance of this window changes. |
| |
6.1 | 25 | |
| |
9.1 | 26 | This window contains **Search** , list **Object Properties** |
| |
6.1 | 27 | |
| |
9.1 | 28 | Exporting a Single Object with Destination **The file** looks like this: |
| |
6.1 | 29 | |
| |
15.1 | 30 | [[image:image-20230425154330-2.png]] |
| |
6.1 | 31 | |
| |
9.1 | 32 | **The search** is performed by the name of all properties in the list. |
| 33 | In the **Object properties** list , in the order of the hierarchy, all the properties of the object are located, namely: | ||
| |
6.1 | 34 | |
| |
9.1 | 35 | All properties |
| |
6.1 | 36 | |
| |
9.1 | 37 | * Are common |
| 38 | *1. Object name | ||
| |
6.1 | 39 | *1. IMEI |
| |
9.1 | 40 | *1. Device type |
| 41 | *1. Object Model | ||
| 42 | *1. Subdivision | ||
| 43 | *1. Telephone | ||
| |
6.1 | 44 | |
| |
9.1 | 45 | * Sensors |
| 46 | *1. (List of available sensors) | ||
| 47 | * Teams | ||
| 48 | *1. (List of available command templates) | ||
| 49 | * Norms | ||
| 50 | *1. Current mileage | ||
| 51 | *1. Hours | ||
| 52 | *1. Normal flow | ||
| 53 | *1. Normal idle | ||
| |
6.1 | 54 | |
| |
9.1 | 55 | * THAT |
| 56 | *1. (List of available maintenance) | ||
| |
6.1 | 57 | |
| |
9.1 | 58 | When selecting multiple objects in the **Export: Select Object** window , we cannot select specific sensors and models. **The Export: Select object properties** window will look like this: |
| |
6.1 | 59 | |
| |
15.1 | 60 | [[image:image-20230425154335-3.png]] |
| |
6.1 | 61 | |
| |
9.1 | 62 | Only categories of properties are available here, without specifying the properties themselves. |
| 63 | In the two cases above, the next step will be to create properties files from the selected objects. | ||
| |
6.1 | 64 | |
| |
9.1 | 65 | **In the following case, if one object was selected in the Export: Object selection** step and the export destination **was Element** , then **the Import: Object properties selection** window opens : |
| |
6.1 | 66 | |
| |
15.1 | 67 | [[image:image-20230425154339-4.png]] |
| |
6.1 | 68 | |
| |
9.1 | 69 | **The Import Type** option has been added . It is responsible for how the selected properties will be written to the object. There are three types of them: **Replacement** , **Merge** , **Addition** . |
| |
6.1 | 70 | |
| |
9.1 | 71 | **Replace** - replaces all properties with previously selected properties in the file. |
| 72 | **Merge** - new data is added to the old. If the old and new elements have the same name, then the old elements are replaced with new ones. | ||
| 73 | **Append** - new data is added to the old. In this case, elements with the same name remain untouched. | ||
| |
6.1 | 74 | |
| |
9.1 | 75 | Selecting the **Replace** type displays all the available properties listed above. |
| |
6.1 | 76 | |
| |
9.1 | 77 | When you select **Merge,** the following properties are available: |
| |
6.1 | 78 | |
| |
9.1 | 79 | * Sensors |
| 80 | *1. (List of available sensors) | ||
| |
6.1 | 81 | |
| |
9.1 | 82 | When you select **Add,** the following properties are available: |
| |
6.1 | 83 | |
| |
9.1 | 84 | * Sensors |
| 85 | *1. (List of available sensors) | ||
| 86 | * Teams | ||
| 87 | *1. (List of available command templates) | ||
| 88 | * THAT | ||
| 89 | *1. (List of available maintenance) | ||
| |
6.1 | 90 | |
| |
9.1 | 91 | * Custom fields |
| 92 | *1. (List of existing custom fields) | ||
| |
6.1 | 93 | |
| |
9.1 | 94 | If a model or division is added that the client does not have, then the new data is entered into the client's directory and written to the object. |
| |
6.1 | 95 | |
| |
9.1 | 96 | By clicking on the **Import** button , the properties selected in the **Import: Select** object properties step, the object selected in the **Export: Object selection** step , will be imported into the objects selected in the **Import: Import destination step** . |
| |
6.1 | 97 | |
| |
15.1 | 98 | [[image:image-20230425154342-5.png]] |
| |
9.1 | 99 | ))) |