You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/exporting/exporting-data.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,17 @@ Monkey365 has built-in support for exporting data to a large variety of formats,
12
12
13
13
## Data Location
14
14
15
-
Depending on what format you are exporting to, the ```-ExportTo``` parameter presents you with slightly different options. Once Monkey365 has finished running, all the exported data are stored under Monkey365/monkey-reports/$GUID/$FORMAT/$FILE. The following demonstrates some examples in which the data may be programmatically accessed using various common languages.
15
+
Depending on what format you are exporting to, the ```-ExportTo``` parameter presents slightly different options. When ```-OutDir``` is specified, Monkey365 writes the exported data to the provided path. When ```-OutDir``` is not specified, Monkey365 creates the output under the current working directory.
16
+
17
+
By default, exported data is stored using the following structure:
18
+
19
+
```./monkey365-output/$GUID/$FORMAT/$FILE```
20
+
21
+
For example, if Monkey365 is executed from ```/home/user/cloud_reports```, the default output path will be:
The following code snippet illustrates how one may load the Monkey365 data in a PowerShell script (assuming that report data was previously exported to JSON format):
The following code snippet illustrates how one may load the Monkey365 data in a PowerShell script (assuming that report data was previously exported to CLIXML format):
0 commit comments