Re: Help please!!! owssvr.dll only returns non null columns

ErnestoM — Thu, 18 Mar 2010 19:44:21 GMT

The FilterOwssvr command in qRules can accomplish this. qRules validates parameters when we pass them in, and in this case, since we don't have a value for /value, it would usually fail. However, it is possible to trick the command by using this command: FilterOwssvr /dsname=owssvr /filter=Year /value="

You can try a URL like this:
http://<servername>/_vti_bin/owssvr.dll?Cmd=Display&List={CD03B0B0-F954-4443-B95C-A52A9242C568}&XMLDATA=TRUE&FilterField1=Year&FilterValue1="

The trick is in bold. Let us know if it works.

Help please!!! owssvr.dll only returns non null columns

Stone 13 — Tue, 12 Jan 2010 20:10:37 GMT

I have a filtered data connection to a sp list, I am filtering the list by passing in the ID of the desired row and programatically creating the url in the format:

http://<mysite>/_vti_bin/owssvr.dll?Cmd=Display&List={GUID}&FilterField1=ID&FilterValue1=734

This returns the data very quickly in a list w/over 8,000 entries however, it seems to omit any columns that have all null values. I'm pulling in this data and users are updating the null information and resubmitting this to sp. Everything works except I am missing a ton of columns, I need all columns to appear even if all values are null so I can bind them to a textbox as the purpose of this form is to get rid of all the nulls.

Data Connections

Re: Help please!!! owssvr.dll only returns non null columns

Help please!!! owssvr.dll only returns non null columns