Messages In This Digest (3 Messages)
- 1a.
- Re: New to SharePoint group and a question From: deanl1440
- 1b.
- Re: New to SharePoint group and a question From: dick_penny
- 2.
- Project Server Custom Field list of options to come from an external From: richardbsargent
Messages
- 1a.
-
Re: New to SharePoint group and a question
Posted by: "deanl1440" deanl144@hotmail.com deanl1440
Fri Feb 24, 2012 7:51 am (PST)
Joe, i recommend creating 2 Custom lists, MOdels and ModelAssignments. In the Models list add the Model number and any other specific information, that is specific to that Model such as manufacturer and serial numer. In the ModelAssignment list, add a Lookup field that is connected to the Model list, rename the default Title field to AssignedTo and an additional Assignment Date column (Date data type).
you will then be able to easily to what you describe. One of the big improvements in 2010 it the ability to enforce referential integrity so that lookup data cannot be accidentally deleted.
If your people are in Active Directory, you may want to make the Assigned To column a People column so that it is easier to choose a person. In this case, you won't be able to use the default Title column in the ModelAssignment list. to work around this problem, create a new custom Content Type that is based on a List item. In this CT, set the Title to Hidden, then add the Model column (as Lookup) and the AssignedTo column (as a Person/Group). Go back to the ModelAssignment list, under Advanced Settings, activate Content Types, add the new CT, remove the original Item CT and then when you create a new item, you won't see the unused Title field on the new item form.
In the Model Assignment list, create a new view that Groups By Model
HTH
Dean
--- In sharepointdiscussions@yahoogroups. , Roger <frontierrog@com ...> wrote:
>
> SP2101? That must be in beta.
>
>
>
> _____________________ _________ __
> From: Joe (Mall of GA) <joebuehler2004@...>
> To: "sharepointdiscussions@yahoogroups. " <sharepointdiscussiocom ns@yahoogroups. >com
> Sent: Thursday, February 23, 2012 12:13 PM
> Subject: [sharepointdiscussions] New to SharePoint group and a question
>
>
> Â
> Hello everyone. I have been using SharePoint 2007 for quite a while and now we are planning a move to 2010. I am familiar enough with SP2101 to be dangerous.
> Â
> One hurdle I have not been able to find an answer to is how to create a DB to store info that can be appended. For example, I have a DB of assets with a user, model and serial number (among many other fields). I want to capture the reassignments of that model/serial combination and be able to look at the history of the one item at any given time. It should also include the date of the change.
> Â
> Model       Serial        Assigned to   Date
> ABC-123  1234567   John Doe       2/23/2012
>                                     John Smith    1/31/2012
>                                     Debbi Jones   1/20/2012
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ricky Thomas 1/15/2012
> Â
> This data will be added to the Asset DB to disply the history, which seems to as simple as a linked record.
> Â
> I hope that is clear enough to understand and thank you for any help!
>
> Joe
>
> [Non-text portions of this message have been removed]
>
>
>
>
> [Non-text portions of this message have been removed]
>
- 1b.
-
Re: New to SharePoint group and a question
Posted by: "dick_penny" d_penny@usa.net dick_penny
Fri Feb 24, 2012 11:33 am (PST)
Joe,
See the articles on "end user SharePoint" by Mark Rackley. He's got a way you can do it with just one list and a custom "new" form.
Dick Penny
--- In sharepointdiscussions@yahoogroups. , "deanl1440" <deanl144@..com .> wrote:
>
> Joe, i recommend creating 2 Custom lists, MOdels and ModelAssignments. In the Models list add the Model number and any other specific information, that is specific to that Model such as manufacturer and serial numer. In the ModelAssignment list, add a Lookup field that is connected to the Model list, rename the default Title field to AssignedTo and an additional Assignment Date column (Date data type).
>
> you will then be able to easily to what you describe. One of the big improvements in 2010 it the ability to enforce referential integrity so that lookup data cannot be accidentally deleted.
>
> If your people are in Active Directory, you may want to make the Assigned To column a People column so that it is easier to choose a person. In this case, you won't be able to use the default Title column in the ModelAssignment list. to work around this problem, create a new custom Content Type that is based on a List item. In this CT, set the Title to Hidden, then add the Model column (as Lookup) and the AssignedTo column (as a Person/Group). Go back to the ModelAssignment list, under Advanced Settings, activate Content Types, add the new CT, remove the original Item CT and then when you create a new item, you won't see the unused Title field on the new item form.
>
> In the Model Assignment list, create a new view that Groups By Model
>
> HTH
> Dean
> --- In sharepointdiscussions@yahoogroups. , Roger <frontierrog@com > wrote:
> >
> > SP2101? That must be in beta.
> >
> >
> >
> > _____________________ _________ __
> > From: Joe (Mall of GA) <joebuehler2004@>
> > To: "sharepointdiscussions@yahoogroups. " <sharepointdiscussiocom ns@yahoogroups. >com
> > Sent: Thursday, February 23, 2012 12:13 PM
> > Subject: [sharepointdiscussions] New to SharePoint group and a question
> >
> >
> > Â
> > Hello everyone. I have been using SharePoint 2007 for quite a while and now we are planning a move to 2010. I am familiar enough with SP2101 to be dangerous.
> > Â
> > One hurdle I have not been able to find an answer to is how to create a DB to store info that can be appended. For example, I have a DB of assets with a user, model and serial number (among many other fields). I want to capture the reassignments of that model/serial combination and be able to look at the history of the one item at any given time. It should also include the date of the change.
> > Â
> > Model       Serial        Assigned to   Date
> > ABC-123  1234567   John Doe       2/23/2012
> >                                     John Smith    1/31/2012
> >                                     Debbi Jones   1/20/2012
> > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Ricky Thomas 1/15/2012
> > Â
> > This data will be added to the Asset DB to disply the history, which seems to as simple as a linked record.
> > Â
> > I hope that is clear enough to understand and thank you for any help!
> >
> > Joe
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
- 2.
-
Project Server Custom Field list of options to come from an external
Posted by: "richardbsargent" rsargent@ema-inc.com richardbsargent
Fri Feb 24, 2012 8:49 am (PST)
Project Server 2010 is a feature of SharePoint 2010 Enterprise, so I am hoping there are some users of Project Server who monitor this group. I want to create a custom field in Project Server that gets its list of possible values from an external list. Out of the box it does not seem to work that way. I created an external list in the home site of PWA. But when I go to create a new custom field, that list does not show up as a possible list to pick for the values for the custom field. In fact, no list on the site shows up unless it is specifically created within the link to create custom fields, and those lists don't show up in the way that normal lists do. So there is something special about these lists. Anybody know of a way to use BCS to define a source for one of these special lists, rather than hardcoding the values?
Need to Reply?
Click one of the "Reply" links to respond to a specific message in the Daily Digest.
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Individual | Switch format to Traditional
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
No comments:
Post a Comment