When you want to submit multiple LegacyFlo requests or schedule automatic submission of requests, the request details have to be submitted via a CSV.
Typically the first row of the CSV contains the headers, where the property/parameter names for the request are defined. The first row of the CSV should not be modified as it contains the parameter names and order of parameter for subsequent records.
The second row on-wards are the LegacyFlo request parameters, one for each request.
The number of parameters and the compulsory parameters depend on the request type. Where a parameter need not be specified, the sample file will contain a "blank".
To build the CSV, it is recommended that you download the sample CSV from the interface and then customize it as per your needs.
Some important points to consider when generating the CSV for Scheduler or when submitting multiple requests are as follows :
| CSV parameter | Submitting Multiple Requests (via LegacyFlo application interface) | Scheduling Requests (via LegacyFlo Scheduler interface) |
|---|---|---|
| Number of requests | Upto 100 requests | Upto 1500 requests |
| Since and Before dates | Used as given | For the Once frequency, the values will be used as specified. For all other frequencies, The values given in the CSV are ignored and replaced with values as per the frequency of the schedule. For example, for weekly schedules, the since will become the date of the Sunday of the previous week and before will be the Sunday of this week. For more details on the schedules, refer to this document. |
| Destination file name (when the doc type chosen is ZIP) | Used as given | For records having user ids: For requests which create files on the destination, the file names given are appended with the time stamp depending on the frequency of the schedule. The time stamp appended will be as given below: Once: <filename>-once-<dd>-<mm>-<yy>.<ext> : E.g. test-once-23-02-24.zip Daily: <filename>-<dd>-<mm>-<yy>.<ext> : E.g. test-23-02-24.zip Weekly: <filename>-<ww>-<yy>.<ext> : E.g. test-34-24.zip Monthly: <filename>-<mm>-<yy>.<ext>: E.g. test-08-24.zip Yearly: <filename>-<yyyy>.<ext>: E.g. test-2024.zip For records having distribution list ids In addition to the time stamp appended, each destination file is pre-pended with the user id <userid>-<filename>-<dd-mm-yy>.<ext> E.g.: johnsmith-test-23-02-24.zip |
| User ID | Only user email ids are allowed. Distribution list ids will not be accepted. | In addition to giving user email ids, for certain request types (see section below), you can specify a Distribution List in the source. When scheduling requests, the members of the distribution list are used to submit individual requests. For example, if you want to schedule copy of Teams data of selected users, you can add these users as members to a DL on M365. This DL id can be added to the single record in the CSV file uploaded to the scheduler. The scheduler will submit individual requests for each member of the DL at the scheduled interval. |
List of Scheduler requests which can take a Distribution List ID in the user ID field
The list of request types which support a Distribution List ID in the user ID field are:
- ONEDRIVE-S3-ZIP
- M365API-S3-PST
- M365API-S3-ZIP
- TEAMS-S3-PST
- TEAMS-S3-ZIP
- TEAMS-VAULTASTIC4
- GDrive-S3-ZIP
- GMAILOAUTH-S3-PST
- GMAILOAUTH-S3-ZIP
- GMAILAPI-S3-PST
- GMAILAPI-S3-ZIP
NOTE: For requests which pich up data from M365, the DL should NOT BE a Dynamic Distribution List