Skip to main content
Nintex Community Menu Bar

9419i15D250CABA8BE505.png

 In Nintex Workflow Cloud the SharePoint Online - Get A File action needs the name of a Document library to get the file from. One obvious choice is almost always there: "Documents". Especially when linked to a team in MS Teams. Seems an easy pick. But when your site is not all English the URL for the Documents library is in another language while it is still named Documents. This actions seems not be able to deal with that properly. 

 

Example: When - once upon a time - you installed your Microsoft tenant and answered "Netherlands"  to the question "In which country is your organisation located?", you're done. All your library names and a lot lot more is suddenly all set to Dutch. Including the language (and folder names) of your teams and a whole lot more. And... it can never be changed anymore. Many know this issue.

In this example the URL for the Documents library of your site is automatically named "Gedeelde documenten".
9420i737B07C4E2D80F68.png

Unfortunately it seems to me after a bit of testing that the Get A File action is not able to cope with this. And possibly some related actions as well.

 

BTW. Dear Nintex, please be gracious: if you're updating these actions anyway, can you please also add the error return code option such as for File not found? Currently you just crash the workflow when the file is not found.

Thanks.

Hello,



 



this is very interesting indeed I would love to look into this with you further. 



 



I have access to a Dutch O365 tenant and NWC so I will be trying to replicate this myself.



 



In terms of the errors these are typically what is returned from the 3rd party service, in this case O365, with the relevant correlationId, we do this as to not generalise the errors potentially removing useful information such as this.



 



I agree that the errors could certainly be a little more descriptive should it be something we can easily identify, I will actually feed this back to the product team.



 



 

Thanks @Jake for willing to look into this. These little bugs hinder. And what I meant with the remark on error message is this: Please return an error code instead of crashing the workflow when a file is not found. I can handle exceptions but nobody wants his workflows to crash.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings