Upload Status Display and Error Tracking

You must define the ‘Error SQL’ and ‘Success SQL’ under the Upload SQLs tab , . These SQL snippets are dynamically appended to the main report SQL post-processing . They must query the dedicated Data View (e.g., `xxen_blitz_report_samp_12867_u`) . This view contains the original uploaded data along with the returned status (`xu.status_`) and message (`xu.message_`) for each record .

It is absolutely critical that both the Error SQL and the Success SQL select the exact same number of columns and in the exact same sequence as your main report SQL extraction query . This is necessary because they are appended dynamically to format the final output correctly , . The SQLs should include human-readable status meanings by using utility functions like `xxen_upload.status_meaning` and `xxen_upload.action_meaning` , .

In an API-based upload, the input parameter `action_` receives values like `xxen_upload.action_create` or `xxen_upload.action_update` from the framework . Your custom wrapper procedure must populate the output parameter `status_` with either `xxen_upload.status_error` or `xxen_upload.status_success` based on the processing result . The output parameter `message_` is used to return the descriptive error or success message that appears in the final Excel output .

The retention of data in the `xxen_upload_data` table is controlled by the profile option ‘Blitz Upload Data Retention Days’ . The default value for this profile is zero . A setting of zero means that the data is deleted immediately during the upload processing . If set to a non-zero value, the data is kept for that number of days, which is useful primarily for debugging purposes .