I am also running into this issue. The FSFileName is provided as pxRequestor.pyFilePath after uploading an Excel document through the FilePath control (PegaGadgets:8-01-01) with .pyFilePath listed as the target property of the control, and the TemplateRFB being passed in is present in the application. Both follow the same formats previously needed for the MSOParseExcelFile activity.

After running this activity with the above inputs and performing an Obj-Save on the page it was run on as well as the page provided for output (outputPageName), there is no data present. These pages are both of the same class. My tracer displays no warnings, errors, or fails when it is run during this process.

Where exactly on the clipboard would the parsed data be written to if not the outputPage or the page the activity was run on?

I'm not sure if anybody tried it yet. It would be good if Pega can confirm if its a bug or not.

Hi , 

The pxParseExcelFile  seems to be working fine. To answer to your question to where on clipboard we can see the parsed data -- We can see that under pyWorkPage-->pySheets. 

Also, attached is a sample document for making a simple pxParseExcelFile .

Thanks

Please mark the answer as Helpful as the related SR is now closed for the same.

Thanks

SR resolved by showcasing how it works. Below is what I observed.

In MSOParseExcelFile, we pass the Template RFB parameter within quotes.

But for pxParseExcelFile, we shouldn't be using quotes for that parameter. It started working after quotes has been removed.

If we parse by sheets, the output will be under PageName->pySheets->List. If we dont use sheet name to parse, it will be PageName->List (Similar to MSOParseExcelFile)

Hope this helps.

Thanks for the confirmation Saravanan.