RE: Connecting and filtering lists

Thanks kris. I figured out my issue yesterday. I had a Listview that
contained the USerID (Domain\USer). I had set the filter up to filter that
column on [Me]. Then i needed the "fire on first Row" functionality from the
dataview webpart so i used FP to convert the DVWP to a LVWP. The Connversion
converted the [Me] variable from the LVWP to the [Current User] variable of
the DVWP. [Current User], i learned, maps to the Fullname field , not the
UserID field so my filter stopped working.
So When using [Me] in a LVWP, i need to add a column for the USERID. When
Using [CurrentUser] in a DVWP, i need to add a column for FullName.

"kris" wrote:

>
> hello man. looks like advanced issue again, as it tends to be with share
> point - on conceptual level all should work fine, but when you get down to
> details you fall onto a minor issue that prevents whole idea woking...
>
> just an idea. why to use separate connected user list to filter projects,
> why not make a dataview version of project list and filter it from dataquery
> level? you can access same current user and current date variables in
> dataview as you can currently in list view.
>
>
> "russgove" wrote:
>
> > We are trying to port a MSAccess app to WSS. The app basically has 3 tables
> > TEAMMEMBERs ( a list of people who can be assigned to projects)
> > teammemberid int
> > teammemberName Char
> > PROJECTS ( a list of projects)
> > ProjectID int
> > ProjectName Char
> >
> > MEMEBRPROJECT(people associated with projects)
> > ProjectID
> > teamMemberID
> >
> > We added two User Information Lookup columns to the TeamMembers Table. One
> > lookup for a user ID and another to lookup a user Name.
> >
> > Our goal is that when a user signs on, we lookup his user id in the team
> > members table, and show him a list of all projects he is on.
> >
> > We added a ListviewWebpart of the teammembers table as the first webpart,
> > then the MemberProject, then the Projects table. We set the connections so
> > that the TeamMembers connected to the MemberProjects and the MemberProjects
> > connected to the Projects.
> >
> > When we display the page each webpart displayed all rows from each list. The
> > teammembers list had a radiobutton next to each row which could be used to
> > filter the MemberProject List, and the The memberproject list had a
> > radiobutton next to each row which could be used to filter the Project List.
> > so far so good.
> >
> > We set the filter on UserName=[Me]. This works great, now the TeamMembers
> > list shows one, and only one row for the currently logged on User. Cool.
> >
> > The problem is that when the user accesses the site, the MEMEBRPROJECT and
> > PROJECTS views show all rows from the lists (they are only filtered after the
> > user clicks then radio button in TeamMembers.
> >
> > We have been trying to figure out how to stop this initial display of all
> > rows from happening. so that a user only sees projects he is assigned to. We
> > wired up a DataView WebPart based on the TEAMMEMBERS table, and found that it
> > has an option labeled ' Send first row to connected Web Parts when page
> > loads'. This looked like just what we needed, when the page loaded the first
> > row in the TEAMMEMBERS table(which is the row for the logged on user) would
> > be sent to the MembersProject list, and that list would be filtered to show
> > only that users projects. The problem is that the Send first row to
> > connected Web Parts when page loads option on the DVWP does not seem to be
> > working. the MEMBERPROJECT table does not get filtered at all... it still
> > shows all the rows.
> >
> > Any Ideas on how we can get this to work.
> >
> >
.