Skip to content

Commit 69186d2

Browse files
JoanneHendricksonVesaJuvonen
authored andcommitted
Update export-amr-api.md (SharePoint#4620)
Content update Expanding content for JobQueueUri to include new job event, FinishManifestFileUpload.
1 parent ddbcd01 commit 69186d2

File tree

1 file changed

+17
-3
lines changed

1 file changed

+17
-3
lines changed

docs/apis/export-amr-api.md

Lines changed: 17 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -173,10 +173,24 @@ Below is an example on how to query the folder:
173173

174174
#### JobQueueUri
175175

176-
public Uri JobQueueUri { get; set; }
176+
public Uri JobQueueUri { get; set; }
177177

178-
The reporting features is the same as createMigrationJob. Logging will be provided to track the status of the asynchronous read. In additional, the log will provide an estimate number of items to be read per url after scan through the database and a rough estimate for your tools.
179-
In terms of blob queue permission and settings, all access will be by default and the same as when the ISV called ProvisionMigrationContainer during the createMigrationJob.
178+
The reporting features are the same as they are for **CreateMigrationJob**. Logging is provided to track the status of the asynchronous metadata read. After a scan of the database and an estimate of your tools, the log provides an estimate of the number of items to be read per URL. By default, blob queue permissions and settings are set to "all access", the same as when the ISV calls **ProvisionMigrationContainer** during the **CreateMigrationJob**.
179+
180+
In addition to the events supported by the Import API (CreationMigrationJob), a new job event called **FinishManifestFileUpload** will be added to the status queue in real time. This is added after the manifest file is generated and uploaded.
181+
182+
As it’s a real time event, ISVs and developers can also immediately download and parse the manifest files once **FinishManifestFileUpload** is generated. Use the field *ManifestFileName* to parse this event to get every manifest file name, including systemdata.xml, usergroup.xml, etc.
183+
184+
The new event will look like this:
185+
186+
```XML
187+
188+
{"Event", "FinishManifestFileUpload"},
189+
   {"JobId", “f8d7d577-676e-47ce-ab69-ae7803979883”},
190+
   {"Time", “2019-09-03T19:11:33.903”},
191+
   {"ManifestFileName", “f8d7d577-676e-47ce-ab69-ae7803979883/ExportSettings.xml”}
192+
193+
```
180194

181195
#### EncryptionKey:
182196
public byte[] EncryptionKey { get; set; }</br></br>

0 commit comments

Comments
 (0)