Server-Side Excel Validation in Blitz Upload

You should use the Excel Validation feature . This configuration involves entering a call to a validation PL/SQL function, mapping its parameters to the relevant SQL columns from the main report . This function executes directly on the server when the user saves the Excel file . The key requirement for your validation function is that it must return a message only in the case of validation failure; otherwise, it must return `null` .

To establish a dependency between columns within the Excel upload, you use the syntax `:$column$.column_name` . This differs slightly from the parameter dependency syntax (`:$flex$.`) . For instance, an Item Description LOV might depend on the Item number entered in an adjacent column using `msiv.segment1=:$column$.item` within the LOV query .

You should check the ‘Read Only’ box against the `CREATION_DATE` column in the Upload Columns list . Checking ‘Read Only’ prevents the column from being updated . Conversely, checking the ‘Required’ box ensures that records are not marked for processing in the Excel file until all mandatory columns are populated .

Yes, if there are columns used internally for processing (such as temporary keys) that the user does not need to see, you can check the ‘Hidden’ box in the Upload Columns list . This makes the columns invisible in the Excel file template .