If you're fighting with the SharePoint ListData.svc with an odd error:
An error occurred while processing this request.
And you are using an OData operator like endswith, you may encounter this error and be puzzled with why it works for some fields but not others.
Tried various theories -- indexed column? use the column in a view? maybe error with the column? -- with no love until Rob thought that it might have to do with empty values.
Turns out that the underlying implementation of ListData.svc doesn't quite like it if you have un-set or "null" values in your text fields. So a query like this:
http://collab.dev.com/_vti_bin/ListData.svc/Test?$filter=endswith(PrimaryFaxNumber, '6481099') eq true
Will fail if there is an item in the list with an empty value for PrimaryFaxNumber.
However, using a nullity check will fix the issue:
http://collab.dev.com/_vti_bin/ListData.svc/Test?$filter=PrimaryFaxNumber ne null and endswith(PrimaryFaxNumber, '6481099') eq true
I have been working on putting together an information architecture/file plan document which shows the layout of artifacts in our SharePoint environment and came across this nice little gem after spending a bit of time putting together my stencils:
As you can see, this is the multi-connector and it seems to work great. But then I realized that it seems that the multi-connector only allows for 6 branches...
Amusing and frustrating because it makes no logical sense to me.