Lesson 33 · 1:50

Export for Submission

Export the four-unit report: the GSE compliance review stops on missing photos and points back to Errors; once they're in, the UAD 3.6 ZIP downloads to Export History.

Watch this lesson in DataMasterSign in to your DataMaster account to watchExport for Submission — UAD 3.6 Multi-Family Report

Transcript

Export for Submission

Validation is down to the photos this assignment didn't come with. Let's see what Export for Submission does with a report in that state. Open Export, at the top of the report.

What it builds

Export for Submission builds the file your AMC, lender or client submits: one ZIP with the UAD 3.6 XML, the PDF of the report, and its photos. Before it builds anything, it reviews the report against the GSE's UAD compliance rules. A report with errors that would block submission doesn't get a file.

The compliance review

Click Export for Submission. The review runs in the background, and the card follows it. Here it stops. The missing room and comparable photos are fatal under the GSE rules, so the card says how many errors must be fixed, and no file is built.

The attempt

Export History records the attempt as Failed, with the time it ran. Nothing was downloaded.

Back to the errors

View report opens the Errors panel, with each remaining issue under its section: the kitchen and bathroom photos in Unit Interior, and the comps' photos in their grids. Add them there, and export again.

The finished file

When the review passes, the build runs: the XML, the PDF and the photos go into one package, the package is checked again with the UAD compliance API, and the download starts on its own. Export History then lists it as Complete, with its file size, and Download gets the same file again at any time. Export again only after you change the report.

Submission

Send the ZIP to your client the way they ask for it, usually through their portal. That's the whole four-unit assignment, from the order to submission.