One of the more popular features in Scribe Insight is the Test Window. The Test Window lets you test your DTS file without actually running it. This is good in some ways because it will let you see what might happen, but it does not let you see what actually happens, because it does not write data to a target. When we were designing a similar capability for Scribe Online we came up with two separate features. One is the Preview feature, which shows you up to 25 source rows and the results of field mappings and non-lookup formulas that are applied to those mapped source field values. The other is the Debug feature, which lets you run your map, block by block, monitoring input values and output values along the way. Debug has controls for stepping through your map and tabs for viewing input and output values. It is a really handy feature to have when you are designing and testing a map. Click the image below to view the Debug tutorial and learn more about the feature. Here are a few things to note about Debug before using it: Debug is available for advanced maps but not for basic maps. The map must be saved. Click Save Map before starting Debug mode. The Agent you selected for this Solution Instance must be running. There must be no errors in the Errors and Warnings tab of the palette (or any individual blocks). Most importantly, when Debug runs your map, it writes data to the target. It is not a preview. Debug has a few simple commands you can use to control it. Start — Start processing this map in Debug mode. Debug will process the first (Query) block, then stop. Stop — Stop Debug mode. When you click Stop, the Solution Instance will become available. The Status (on the Solutions page) will display as Last run failed. Next — Process the next block in this map. While Debug is running, there are three tabs you can you to monitor what is going on. Current — When you run Debug, the Current tab displays all of the fields that are available for processing by the current block. Global —Depending on your map, there may be a subset of globally available fields that will be displayed on this tab. For some operations, after a block finishes processing, the Global tab displays the Input fields for the previous operation. In general, however, the Current and Global tabs will display identical information. Record Errors — If Debug encounters a record error, such as a data type mismatch, invalid field formula, or truncation error, the Record Error tab opens to display the error. Other notes about Debug: If the Solution Instance is scheduled to run while you are in Debug mode, the Solution Instance will not start until you stop Debug mode. When running in Debug mode, other users will see the Status for this Solution Instance as In Progress. If you are using a Connection with batch processing enabled, you will not see any row errors within Debug until an entire batch completes. Scribe suggests that you create a very small batch for Debug testing (either using a Query filter or by changing the batch size). Debug mode uses the valid Connections and Agent for the map you are debugging. However, Scribe Online does not write record errors or update the fields used to track the most recent record processed. Do not expect Debug to be blazing fast as it is running your map. There are a lot of things going under the covers when Debug is running to be able to present information on the screen and to have stopping point enabled. However, the speed at which Debug runs is no indication of the speed that your Solution Instance will run when in non-debug mode.
↧