🖥️For BizOps Pros

FlightPath is a technical tool, similar to an IDE or Azure Storage Explorer. While a BizOps team member might not use all of FlightPath's functions, in our experience Excel wranglers are totally capable of picking it up and quickly getting value from FlightPath.

What file was staged most recently

  • Click the Find data button at the center of the home screen.

  • In the drop-downs, select files and the named-file you are looking for

  • In the text box enter the path, arrival date, range, or fingerprint of the file you are looking for

  • When you see the file in the list of results, right-click to open the metadata or the file

  • If you want to use the file as test data, right-click on the file in the named-files window and select Copy to working dir. This copies the immutably staged file back to the project directory so you can work with the data.

What script was used in the last run

  • Use the Find data button to open the Find files by reference dialog. Select results and the name of your results.

  • In the text box replace :all with :last or just right click on the last item

  • With the run time and named_paths_uuid open the named-paths. (The name will always be the same as its results).

  • Open the named-paths manifest.json and find the entry for the time period with the same UUID.

  • Look at the named_paths key to see the exact CsvPath Language statements used in the run.

What where the errors in the most recent run

  • Use the Find data button to open the Find files by reference dialog

  • Select results and your named results.

  • Add :last to the textbox. Add a partial path or date, if needed.

  • Right-click the last item shown in the results list. Select Show run.

  • Click to open the run manifest.json

  • Look at the error_count key to see the total errors in the run.

  • Click on the directory containing the results of an of the csvpaths in the run. Inside you will see the errors.json file containing all errors from the run. Within errors.json each item in the list of errors, if any, has a message key with the built-in or user-defined error message.

  • Depending on how the csvpath was written, there may be useful error-related info in the printouts, if any. If a printouts.txt file was generated, click on it to check.

Last updated