February 10, 2012  
   Login  
Forum  
 
ForumForumEnesys RS Data ...Enesys RS Data ...Support - RS Da...Support - RS Da...Getting not a valid column nameGetting not a valid column name
Previous Previous
 
Next Next
New Post
 12/8/2009 10:05 PM
 

Trying to add a column to condition in query builder using visible columns list. But when I run it I always get error not a valid name column. What am I doing wrong?

New Post
 12/8/2009 10:43 PM
 

HI,

Could it be some custom column added through a feature or something like this?

Do you get this problem whatever the column you are using in a condition?

Regards,


Frederic LATOUR
ENESYS
New Post
 12/9/2009 4:30 PM
 

Well not every column. If I use column called title it works fine , but with all other columns its is a problem.

New Post
 12/9/2009 5:09 PM
 

Hi,

Would you mind sending me the list template (.stp) by email to our support address ( support  at enesyssoftware dot com).


Frederic LATOUR
ENESYS
New Post
 12/10/2009 5:42 PM
 

Hi I dont feel comfertable sending list template, as I do not have my client authorisation for it. I need to get this working to demo it to my client, if they need to deceide on buying your data extension. Here is what I am getting.

Error while executing query

[column] is not a valid name column. FieldRef node: <Field Red Name="column" />

I have no problem getting data from that particular column.

New Post
 12/10/2009 5:51 PM
 

BTW I am using rolluplists . I should be able to query  based on different criteria to query same list in different sites. Just for reading data without any query works fine.

New Post
 12/11/2009 4:54 AM
 

Hi,

I can’t see anything wrong with providing us with a list template until you are not including the data.

One reason, I’m asking for the template is that I would like to check if you are using custom fields. You haven’t answered my question on this.

The problem you are encountering is typical of custom fields for which the xml schema contains some namespace definition which is not necessarily a good thing. This conflict with the namespace used by SharePoint Web Services (though we could certainly adopt a schema agnostic approach for parsing which is not currently the case). That said, the problem could be something else but if you don’t provide me with concrete information it will be difficult to investigate.

Regards,


Frederic LATOUR
ENESYS
New Post
 12/11/2009 4:52 PM
 

Hi,

If you are using RollUpLists, the reason of this message is certainly due to the fact that you are applying a condition to a column that does not exist in one of the lists that is rolled up. Is this situation expected on your side? I mean to have some lists that do not have the specific column you are filtering on?

You should only apply condition to columns that are available in all lists even though you can select such a column wich will not contain any data for such lists that do not contain the specific column.

An alternative for filtering on such a column is to filter either using a "SqlQuery" statement or at the report level. Of course, on a performance standpoint, it is much better to filter at the "RollUpLists" statement level because the filter will take place at SharePoint level.

Does this make sense? Let me know if you need further information.

Regards,


Frederic LATOUR
ENESYS
Previous Previous
 
Next Next
ForumForumEnesys RS Data ...Enesys RS Data ...Support - RS Da...Support - RS Da...Getting not a valid column nameGetting not a valid column name

 
You need to login for posting to the forums.
If you don't have a login, click here to register.
 
Copyright 2010 Enesys - All rights reserved Terms Of UsePrivacy Statement