[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 232
  • Last Modified:

New to Sharepoint 2010.

My company has decided to move into SharePoint 2010 for data warehousing and for use by many different departments. As it stands I have no experience in SharePoint and am need of some pointers. What I am trying to accomplish is to store all my lists in a single site or site collection to which I will grant the least amount of privileges to and then created other sites or site collections to which my users will actually go and work from. I need to find a way to allow users to access forms and data from the single “Lists” site(collection) and work with that data and have workflows run on that data across different lists. For instance, HR will need an Employees list where they enter employee info. When that is submitted I need it to email me in IT to create accounts and grant that user access, as well as notify Finance of the hire. When HR terms an employee or someone changes roles I need workflows to notify the responsible people to take the required actions, i.e. IT disables the employee’s accounts. Basic can anyone point me to a resource for someone new to SharePoint 2010 to connect lists to a different site or site collection?
0
CooperRiis
Asked:
CooperRiis
  • 2
1 Solution
 
CooperRiisAuthor Commented:
I realized that my example above was not complete enough to explain the situation. The reason a single workflow would not work for the above example is, after IT is notified we need to publish their account information into their employee record. In other places an employee’s email address will be pulled from their employee record in the Employee list in order to give feedback based on processes happening in other departments. As well, an asset list will be present for assets assigned to employees i.e. cell phones and laptops. This needs to be readily tied to an employee’s record in the Employee list for the instance of termination where a supervisor will need a list of all the assets that will need to be returned by the Employee. This is just one example of many complicated database style interdepartmental lists that will need to be tied together on a central site that employees will not be accessing directly.
0
 
Ted BouskillSenior Software DeveloperCommented:
Well, I'm not surprised you don't have an answer.  This seems to be a simple request but it's actually complex.

First off, a single master list will create more problems that you realize and SharePoint was not designed to work optimally that way.  If you need to create a master list of employee information I'd use a SQL database that can then be bound to multiple SharePoint lists using custom content type's that are connected to the database tables.

Essentially everything you are asking for is possible with SharePoint but requires and advanced knowledge of the product and this is not the forum to teach you SharePoint.  I'd recommend you hire a consultant to help or start by installing the product in a development environment and start learning it.
0
 
CooperRiisAuthor Commented:
I am taking some courses now. I appreciate the suggestion about Sql. That will most likely be the way I go.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now