Wiki source code of Export objects
Last modified by Андрей Калиновский on 2023/04/26 11:26
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% class="wikigeneratedid" id="H42D43A44143F43E440442" %) | ||
2 | ((( | ||
3 | Export window: Object selection is invoked by pressing the button in the Export column, in the Objects line. | ||
4 | |||
5 | == Export: Select object == | ||
6 | |||
7 | Options: **Export destination** , **Search** , list of objects | ||
8 | At this stage, select the export destination and the objects that we want to export. | ||
9 | |||
10 | [[image:image-20230425154324-1.png]] | ||
11 | |||
12 | **Destination of export** - a field, when clicked, a list of two options drops out: **File** and **Element** | ||
13 | |||
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** . | ||
16 | |||
17 | **Search** - it is possible to search for objects from the list in the string. A search is performed by Object, Model and IMEI. | ||
18 | |||
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. | ||
21 | |||
22 | == Export: Select object properties == | ||
23 | |||
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. | ||
25 | |||
26 | This window contains **Search** , list **Object Properties** | ||
27 | |||
28 | Exporting a Single Object with Destination **The file** looks like this: | ||
29 | |||
30 | [[image:image-20230425154330-2.png]] | ||
31 | |||
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: | ||
34 | |||
35 | All properties | ||
36 | |||
37 | * Are common | ||
38 | *1. Object name | ||
39 | *1. IMEI | ||
40 | *1. Device type | ||
41 | *1. Object Model | ||
42 | *1. Subdivision | ||
43 | *1. Telephone | ||
44 | |||
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 | ||
54 | |||
55 | * THAT | ||
56 | *1. (List of available maintenance) | ||
57 | |||
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: | ||
59 | |||
60 | [[image:image-20230425154335-3.png]] | ||
61 | |||
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. | ||
64 | |||
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 : | ||
66 | |||
67 | [[image:image-20230425154339-4.png]] | ||
68 | |||
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** . | ||
70 | |||
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. | ||
74 | |||
75 | Selecting the **Replace** type displays all the available properties listed above. | ||
76 | |||
77 | When you select **Merge,** the following properties are available: | ||
78 | |||
79 | * Sensors | ||
80 | *1. (List of available sensors) | ||
81 | |||
82 | When you select **Add,** the following properties are available: | ||
83 | |||
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) | ||
90 | |||
91 | * Custom fields | ||
92 | *1. (List of existing custom fields) | ||
93 | |||
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. | ||
95 | |||
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** . | ||
97 | |||
98 | [[image:image-20230425154342-5.png]] | ||
99 | ))) |