We have a SharePoint form library that was built using InfoPath 2003 and SharePoint 2003 and uses form fields/library columns to filter data with for information hiding/ease of access (using Greg Collins' http://www.infopathdev.com/blogs/greg/archive/2005/09/08/Use-the-SharePoint-_27005B00_Me_5D002700_-Filter-with-a-Promoted-Property.aspx method). Over the weekend we upgraded to MOSS 2007 and are having problems with view that previously used the [Me] property.
Previously in SharePoint 2003 we could use the value [Me] as a filter to indicate the current user. After the MOSS 2007 upgrade this filtering value no longer seems to work/be valid for columns with a data type other than “People and Groups”. The problem is that all the views are based on this filtering and currently due to the strictness of the view definitions, most of the users cannot access the data they should have access to. The problem is that after the MOSS 2007 upgrade the filtering no longer works on fields that are Text/String and users cannot access the cases they should be able to see.
We think this is due to the following and we need help fixing it. The fields that the views filter on are defined by InfoPath as a “Single line of text” in a data type of “Text (string)” and we cannot change this datatype through SharePoint like we can for columns created directly in SharePoint. InfoPath 2003 also does not have a data type for “People and Groups”.
Perhaps if we could use a Custom (complexType) in InfoPath 2003 to refine the data type of the problematic fields to the MOSS 2007 equivalent of “People and Groups” then the filtering value of [Me] would work. We would need to know the namespace for the datatype though as the user's editing the form do not have access to InfoPath 2007.