When automating processes with Blue Prism, integrating digital assets such as the "PDF to Excel Converter" from the Digital Exchange can significantly streamline workflows. However, users occasionally encounter errors. This article addresses a specific issue: the "Invalid Index" error (Exception from HRESULT: 0x8002000B (DISP_E_BADINDEX)) when using the "Save As" function in the PDF to Excel Converter.
The error arises during the code stage execution when the Blue Prism process attempts to save the converted Excel file. The "Invalid Index" exception typically indicates a problem with the parameters passed to the SaveAs
method.
Based on community discussions, here's a breakdown of potential causes and solutions for this error:
SaveAs
Code StageSaveAs
function requires specific parameters, including the filename and file format. If these parameters are incorrect or mismatched, the "Invalid Index" error can occur.SaveAs
code stage match the required format. Consider the following:
51
is typically used for .xlsx
files.wb.SaveAs(filename, 51)
C:
drive for testing purposes. Update the Blue Prism process with the new file path and re-run the process, if you get the same error the next thing to try would be to move the pdf to another folder location for example on your desktop and then run the process again with the new location for the pdf as the input.If troubleshooting steps do not resolve the error search the community forum.
The "Invalid Index" error in Blue Prism's PDF to Excel Converter can be perplexing, but a systematic approach to checking parameters, file paths, and filename manipulation can often lead to a resolution. Leveraging the Blue Prism community and its wealth of shared knowledge is also invaluable in overcoming such challenges. Remember to validate your settings and seek help when needed to ensure successful automation.
This article provides general information, for specific solutions, Refer to the community here.