RE: Using a Calculated field in List A as a Lookup field ref in Li

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Cayzee & Parag,

I have a similar need. I have a PO list and PO Items list. When a certain
PO is selected, then items for that purchase order should show. It's a
frustrating problem that MSFT needs to address in their next round of
software offerings.

Regards,
Ron_D

"Parag Sinkar" wrote:

> I dnot think that's possible even with CAML.
>
> While creating Linked Lists you can only create links with a "COLUMN WHOSE
> DATATYPE IS SINGLE LINE TEXT".
>
> Parag SInkar
> --
> SharePoint Rocks
>
>
> "Cayzee" wrote:
>
> > Here is what I am trying to do. I have a List A with an ID and Title fields.
> > I have added an additional calculated field to list A with formula
> > "=concatenate([Title], " - ", [ID) and named the field IDandTitle.
> >
> > In another list B, I want to add a lookup field which looks up the info in
> > List A and uses the IDandTitle field as the fieldref, i.e. the field that
> > appears in the dropdown.
> >
> > The problem is, when defining the lookup field in List B, when I select List
> > A as the lookup list, the only choices I get for Lookup field are ID and
> > Title, and not the calculated field I added to List A.
> >
> > I need this because I have a parent child relationship between List A and
> > List B. And using web part connections, I want to display the child records
> > in List B when someone selects a parent record in List A. The issue is that
> > the Title field in List A can have duplicate values. So if my connection is
> > based on the Title field, I will see the children records for multiple
> > parent records with the same title. I have a choice to use the ID field as
> > the lookup, but that is not very user friendly because when someone is
> > creating a List B records and click on the drop down for the lookup field,
> > all they see is a bunch of numbers. So my solution was to create a
> > calculated field in List A and use that as the drop down in the lookup field
> > in List B and base my web part connections on this calculated field.
> >
> > How do I solve this problem? That is, how do I use a calculated field in a
> > list for lookup in another field?
> >
> > Thanks
> >
> > Cayzee
> >
> >
> >
.

Relevant Pages

  • Re: Custom list (via template) with lookup field to other custom list?
    ... That is going to be tough since the lookup field using the list's GUID ... > defined two new custom lists (by following the steps outlined here: ... > To create the XML for the fields in the list definition schema.XML file, ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: Parent/Child Connections
    ... the WO_Num value to WP2 on first display so that WP1 shows all WO's but WP2 ... you are in the very high likelihood of the two lists getting out ... I wonder every time I see the Lookup field used like this and then ...
    (microsoft.public.sharepoint.windowsservices)
  • List Templates with lookup fields
    ... lookup field becomes broken. ... But when I save an entire site as a template, ... site's collections of lists, new sites based on this template contain the ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Parent/Child Connections
    ... I wonder every time I see the Lookup field used like this and then ... >> Microsoft Office FrontPage ... >>> a parent/child relationship between two lists. ... >>> the cases in the parent table. ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Using a Calculated field in List A as a Lookup field ref in List B
    ... While creating Linked Lists you can only create links with a "COLUMN WHOSE ... > I have added an additional calculated field to list A with formula ... > The problem is, when defining the lookup field in List B, when I select List ... > in List B and base my web part connections on this calculated field. ...
    (microsoft.public.sharepoint.portalserver)