I have Excel sheet representing a survey that shall be dispatched to different departments (based on one department field). How can this be done with the help of SharePoint? Note that each department can only see the result (charts) pertinent to it.
You could host the Excel file in non-searchable document library and create some chart web parts that relate to different department.
This can't be done with a full security based on the excel contents, so if you want to have full security you must create multiple files.
Related
Novice in Sharepoint and looking for some advise.
we are trying to setup a infopath form with the below fields.
ReqID (Autogenerated with a workflow based on ID like Req-1 etc.),
Description,
User,
Date,
Testing,
Tester,
Date
when the user submits the form, we would like to save the information to two separate lists on sharepoint like...
List A - ReqID, Description, User, Date
List B - ReqID, Description, Testing, Tester, Date
Can someone please advise if this is doable without using any coding.
Thank you so much for all the help.
Several possible solutions:
One list:
If it is a matter of hiding clutter from selected users then: create one list for all of the fields and then create two views, one with your first set of columns and the other with the second set of columns. This has the advantage of no duplication of data, and if you need to update the Description column, it only has to be done in one place.
Two lists:
From the InfoPath form, post all of the fields to the first list and create a View that only displays what's needed for the "A" users. Create a workflow that adds a new item to list "B" with only the data needed.
Three lists:
From the InfoPath form, post all of the fields to a master list. Create a workflow that copies selected fields to List A and to List B. This has the advantage of the master list being an unchanged source of the original data for audit or tracking purposes.
Using Web Services
I believe InfoPath can call web services. This will be more like "coding", but you can write data directly to SharePoint lists using SharePoint's REST API.
I'm not sure if the title is a proper descriptor of what I'm trying to achieve here, hopefully it's close enough. I'm not a SharePoint expert, but I'm comfortable with creating forms and workflows as necessary to get something like this to work.
Basically, I need to have two separate SharePoint lists that are linked together, but one list needs to have row level security to hide data from other users that shouldn't see it. I need the column that is being linked to be an editable text box though, rather than a simple lookup field.
For example:
List A
Customer (text)
Description (text)
Sales People (person, multiple selections allowed)
Expenses (linked field)
List B
Customer (text)
Expenses (number)
Created by (just a reference that the sales people would actually "create" each row here)
Essentially, multiple people can be assigned to a customer in list a. The "sales people" are assigned by another user who actually creates the item for list a. I need to be able to have the people who are assigned as "sales people" to have a text box where they can enter their expenses, but on an individual basis, that would then be stored in list b with row level permissions to prevent them from seeing each others expenses totals.
List B would be able to show each sales person their full list of expenses across all the customers they are connected to, but not be able to see each others expenses. It's not a problem if the person creating the item for List A ends up with items in List B that are 0, but I need to be able to have the Expense field be an editable text box from a form that allows the sales people to enter their total expenses for that customer.
If I was building a custom application, this wouldn't be difficult to do, but I can't for the life of me figure out how to do this in SharePoint, or if it is even possible.
This is possible, but it will require custom development, using the SharePoint Object Model. Create your two lists and then you can either create a javascript/HTML based solution using libaries like jQuery and SPServices, or you can create a custom web part and use C# to update the lists. There's lot of examples out on the internet on how to do this. Write some code, and bring any problems you have with the code back to StackOverflow.
I have two related lists in SharePoint that I would like to export to Excel so that the information can be viewed in a nested scenario as it is a one to many situation where list 1 has client information and list 2 has all the purchases related to the client. These are already linked using the OOTB Related Lists functionality in SharePoint. Is this even possible? I have already been able to export each list independently, but was hoping for a scenario where users could go to one Excel sheet and see all the clients and then expand/collapse the purchases.
Thanks!
K.
Use excel to create two worksheets and link them to those lists.Then create a third worksheet to join the other two worksheet. You can find more info : https://superuser.com/questions/420635/how-do-i-join-two-worksheets-in-excel-as-i-would-in-sql.
If you want to go further, instead of lists, you can have the data on an sql server (external content types/lists and BCS), so the join could be done to server and the excel would get all the data. It depends on the amount of data.
So I am trying to link an employee metrics pivot chart with an employee project table with one slicer. I want an employee slicer that manipulates all charts but the data is coming from 2 different places (SQL, Sharepoint). When I try to create a relationship based on Employees I get the following error: "The relationship cannot be created because each column contains duplicate values. Select at least one column that only contains unique values."
So one chart has quantitative items while the table has qualitative items and I want one slicer to manipulate both at the employee level.
I want to see all the data on both charts for the selected employee, and not just single items linked by unique values. I can use unique values, and have created relationships that one slicer can manipulate however I only get one record at a time that way and therefore the slicer has thousands of buttons (one for each record).
I wouldn't think this would be that difficult and I hope it's really not.
Please Help!
M2M relationships in PowerPivot will most likely cause more headaches than solutions unless you are aware of what you are doing. After some thought, I realized that I really do not want an m2m relationship because it would result in junk data for what I wanted. I just wanted to start my answer off acknowledging that I did not achieve an m2m.
So if you want to link SharePoint data to Excel here is what you need to do:
Export SharePoint data as an RSS feed. If this is something others will need to refresh then the rss file will need to be stored on a shared drive.
Add PowerPivot if you have not already done so. In PowerPivot get external data from other sources (rss feed) then add your file. To link data you will need a Unique ID to join tables on.
I'm very new to using SharePoint. I have created a custom list that I use as a linked table in Access. As the access database pre-existed, i need the column names in my SharePoint List to match those that are in the Access Database, otherwise all my Reports & Queries etc will not work.
Is there a way to have a separate display name for the columns in my SharePoint List.
For example, the column names are currently like "Innov_Desc", which isn't User friendly. When the users are adding "New Items", I need to display "Description" for example.
Any help will be appreciated.
Thanks
Derek
If you are trying to do this change from the the user interface (from settings), I'm afraid it's impossible. You will have to do this change in the code.
Please check the links below to get general idea of what is involve when naming columns:
Finding the internal name and display name for a list column
SharePoint Column/Field Display Names vs Internal Names
You can change the display name to something more user friendly via the UI after the column has been created. The internal name of the column will remain whatever it was at the point of creation.