🎇How to Process a File
Last updated
Last updated
Osmos AI Data Wrangler is run natively inside Microsoft Fabric as a Workload. Once added to the organization and you as a user, the Osmos Workload will become available in your home workspace.
The Fabric homepage displays a set of experiences you can run. These experiences are also called Workloads. Select the Osmos Workload to begin cleaning and transforming your file.
Go to Microsoft Fabric, https://app.fabric.microsoft.com/home
Select the Osmos Workload
Note: If the Osmos Workload is not present on your home page, either you have not been given access or the Workload has been enabled for your organization
In this step, select the Workspace where the AI Data Wrangler resides.
From the sidebar, select Workspace
Select the Workspace where your AI Data Wrangler resides
Click on the AI Data Wrangler
In the Osmos Wrangler, you will select the file(s), you wish to process.
Click on the Choose File icon
Choose the Lakehouse that contains the source file and hit Connect. Note, that the Lakehouse selected will turn light gray when selected.
Select the file(s) and hit Save. The source file(s) will automatically begin to process.
Once you select your file(s), they will be listed on the bottom half of the Workload.
Each file will have a status that updates as it moves through the cleaning and transformation.
Statuses include:
Queued
Processing
Ready for Review
Completed
Failed
Rejected
Review and Approve your file(s) before writing to the Lakehouse.
Select Ready for Review
To accept and to write to the destination, select Approve.
If you want to dispose of the current process, select Reject. The file will not be written to the destination.
It will update to a Failed Status.
Reasons for rejection may vary. For example, the user initially chose the wrong file to process.
If you select Retry, it will process the file again.
It will not save the outcome of the previous run(s).
The most common scenario for Retry is to incorporate column descriptor updates.
For more info see the section on Schema Descriptors