Skip to main content
  • EN

Good afternoon

I have a workbench that is using the sharepoint reader to to pull the contents of a list into fme, where when I run it fme reports Microsoft SharePoint List Reader: Client-side error: '404 Client Error: Not Found for url: https://........

The list has ~95 fields in it (so quite a few and the url call is quite long). Through trial and error I have found that there are a couple of fields that if I exclude from the Reader the workbench runs ok. The fields are type string line of text in sharepoint. They have / characters in their names (but so do some of the other fields). None of the records in the list actual have any values entered in those fields at the moment (but there are others like that which read ok) and so I'm a little stuck as to what's causing the error.

These are the 2 bad-eggs

 

I dont' have any Features to Read parameters set in the Reader.

 

Has anybody out there run into a similar issue with the sharepoint reader?

@mark2atsafe I see a few sharepoint q7a with your name against them.. :-)

 

Using Build Desktop 20200

 

Hi @tfhb Please submit your problem to us via https://www.safe.com/support/report-a-problem/ Thanks!

I am getting the same issue with 2020. SharePoint list reader creates all the attributes in the reader fine, but as soon as I try to view the data or run to an Inspector, I get the same error.

 

 

It works when set "Show all Fields" to "No" as it cuts down on the number of attributes considerably.

Has there been any progress on this?

I am getting the same issue with 2020. SharePoint list reader creates all the attributes in the reader fine, but as soon as I try to view the data or run to an Inspector, I get the same error.

 

 

It works when set "Show all Fields" to "No" as it cuts down on the number of attributes considerably.

Has there been any progress on this?

Hi @david.benoit Unfortunately there hasn't been any progress yet. Your issue might be a bit different. Please send details of your situation to https://www.safe.com/support/report-a-problem/ Thanks!

Hi @danatsafe - an update/solution; It turns out that the issue wasn't so much that there were any issues with the couple of fields that I was turning off created the read error, but instead (maybe) the issue was caused by the length of the url call. I've been able to work around the error by using two readers to the same sharepoint list, reading the fields that caused the reader to fail through the second reader and using a FeatureJoiner to combine the sharepoint list features and continuing into the workbench processes from there. Perhaps there is a limit on the length of a url call?

Reply


Community Stats

29,736
Posts
112,990
Replies
37,383
Members
Terms & ConditionsCookie settings