InfoPath Dev

Hi all, I have an odd one for you. I developed a form a while back that happily submits on Windows XP but does not work properly when submitted from a Windows 7 machine. The form is added to the SharePoint list and contains all of the correct data. All of the published fields from the form are updated on the SharePoint site. The problem is, ...

Ok... I have added the xsl:param RowFilter further up and now the error message is: "XSLT transform failed : 0x80004005 : Reference to variable or parameter 'Rows' must evaliate to a node list."

Now I know this is an Infopath site but the people on here are so brilliant with XSL and XML I thought I would try this one anyway. I am trying to filter a data view web part in SharePoint 2003 but only when the filter is actually populated. <xsl:choose>  <xsl:when ...

The expression in the secondary data source will evaluate against all data sources, but mostly primary from what I understand. Are there any script examples of this being done or suggested methods for me to get started on?

Yes, you will need to filter the column where titlle = dropdown value otherwise it will only ever return the first entry.

Hi guys, I have an XML data source which has an XPath expression in one of the columns being pulled in. This column will evaluate to true or false based on other elements in the data source. Is it possible to process the data source and make it evaluate that XPath expression rather than display it as a string? I thought this would need to be ...

Never mind, I worked out where I had gone wrong. /dfs:myFields/dfs:dataFields/dfs:Stacks[not(@Stack_Name = preceding-sibling::dfs:Stacks/@Stack_Name)] That works.

Hi all, I don't know what I am doing wrong here. I have a filter on a field from a SharePoint list and for some reason it is not returning unique values. It is returning all values. /dfs:myFields/dfs:dataFields/dfs:Stacks/@Stack_Name[not(. = preceding-sibling::dfs:Stacks/@Stack_Name)] I have used this approach before and it has worked a ...

If I understand you correctly, I would suggest that an XPath filter on each list might be easier. You only have one list so on the first list you show directorate and make it unique by applying this filter: not(@Directorate = preceding-sibling::dfs:ListName/@Directorate) You make the second list unique and also filter it against the selection ...

Jimmy, you're a legend. I adopted it to match my code and made all the relevant changes for missing SWID elements etc. and it works a treat. Thanks very much. I can't believe I missed insertBefore!