ALL SOFTWARE EXERCISES
- EXERCISES HOME PAGE (813)
- Access 2010 (66)
- Access VBA Macros (17)
- Advanced VBA (29)
- Excel 2010 (83)
- Excel 2013 (10)
- Excel 2016 (0)
- Excel VBA Macros (37)
- Power BI - Excel 2013 (25)
- Power BI - Excel 2016 (23)
- Power BI Desktop (26)
- PowerPivot 2010 (26)
- Report Builder 3.0 (42)
- SQL (156)
- SSAS - multidimensional (21)
- SSAS - tabular (29)
- SSIS Integration Services (40)
- SSRS Reporting Services (53)
- Visual Basic (45)
- Visual C Sharp (65)
- WPF - Visual C# (20)
SSIS INTEGRATION SERVICES EXERCISES
Exercise: Use an OnError event-handler to show errors in script y
This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.
The answer to the exercise will be included and explained if you attend the relevant Wise Owl course (sadly, only in the UK for now).
You need a minimum screen resolution of about 700 pixels width to see our exercises. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.
Create a package to import data from the Excel workbook in the above folder (you may be able to amend a package you've created earlier):
A data conversion task to attempt to convert the item id into an integer.
This package will fail when you run it, because the item numbers shown below can't be converted to integers:
The yellow cells can't be converted to integers.
Attach an event-handler to the OnError event of the data conversion task so that it displays the description of the error.
You'll need to pass the ErrorDescription system variable into the script task for the event-handler.
Rerun your package: you should now see an error message on screen looking something like this:
Here we've added a title and some introductory text to the error message.
If you're feeling energetic, you could always try using a ReadWrite integer variable to track the number of errors, to ensure you only display a dialog box like the one above for the first error.
When you've got this working, close this package down!