The CUST_TABLES$UPD_SUBMITTED_DATA stored procedure is automatically available through the DSU and contains a commented out SQL script for updating a custom table. However, the script needs to be modified by each school ensure the mapped data is saved to the appropriate customized table. The CUST_TABLES$UPD_SUBMITTED_DATA stored procedure contains a sample process detailing how to retrieve data from the internet submission and insert it piece by piece into the mapped custom tables and columns. To use that process, uncomment the code. To process all of the columns for a single mapping table at once, you can use an insert or update statement that reads in and then processes all of the columns for each table at one time. Regardless of whether you use the commented out process or create your own, you will need to add code to manage the insert or update of the submitted data based on the primary key columns that have been defined for the custom table(s) because that information is unknown to J1 Desktop. Jenzabar recommends working with your IT staff to make these updates.

Click this button to run the CUST_TABLES$UPD_SUBMITTED_DATA stored procedure.

If the stored procedure was unsuccessful, an error message appears, the Run Stored Procedure button remains enabled, and the sunburst icon still appears. If the stored procedure was run successfully, the Run Stored Procedure button is unavailable and the sunburst icon no longer appears.

Click this button to view the InfoMaker report for the custom submitted information. The report includes column headers and the data for custom mappings showing the content of the Custom Data tab. Also, you are able to print this report.