Sharpoint Output Error was working fine in December.

Greetings,

I have a workflow that is publishing to Sharepoint, that was working fine prior to the holiday season, this morning its resulting in this error.

Did something change?

Error: SharePoint Output (33): WorkflowRuntimeError("Error while uploading file 'Alteryx Customer List.xlsx'.") has type WorkflowRuntimeError, but expected one of: bytes, unicode

Any ideas would be appreciated

Error Message

Output

Sharepoint

Accepted answers

mceleavey

Hi @BAvitia23 ,

this looks like the data type of a specific column has either changed in your workflow or on the actual list itself.

If you are outputting to a list you need to map exactly what is on the list. For example, if you have a column which only allows a single character and you try to output a column with more than one it will error.

Check all your data types for each column are correct, the data within the columns is correct and all fields are mapped.

Hope this helps,

All comments

mceleavey

Hi @BAvitia23 ,

this looks like the data type of a specific column has either changed in your workflow or on the actual list itself.

Check all your data types for each column are correct, the data within the columns is correct and all fields are mapped.

Hope this helps,

mverworn

I'm having the same problem. I'm overwriting the Excel file, so matching existing fields is irrelevant.

Gumerdrew

Hey all - thought I'd drop my fix to this here in case others run into this problem. I was mysteriously running into this problem with the SharePoint Output tool as well, multiple flows that use this tool started throwing this exact runtime error with no changes from my side. After scouring community for a fix and finding nothing, I started suspecting that something must have changed on the SharePoint side.

Turns out there was an internal DL change in outlook that removed my write access to the folders I was trying to write to with Alteryx, every folder/file I needed was magically read-only now. I reached out to an admin who was able to restore my write access, and this error cleared.

Hope this helps!

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703