However you could create a custome list in standard view and create all the "read-only" columns as calacated fields. When the user clicks on new item they will only have the ability to enter the one editable field. Someone could have a personal view of the datasheet view to export to excel.
Or you can create a link list in excel where you can lockdown any field you want.
I've now sussed out how to create the linked list in Excel and publish it to Sharepoint as you suggested. The problem is that if I lock any of the columns in Excel, I can't create / publish the list to Sharepoint.
I tried using calculated formulas in Sharepoint but couldn't get this to work either.
Can you give an example of you end goal. What is the one editable field(Type and define) that you are creating and what are the calculations based on that field?
- Date payment received
- Payment no.
- Payee
- Currency
- Amount
- Who is responsible for actioning the payment
A single administrator will receive payments off a fax machine and enter them into the log. Users will view the log and tick off the ones that they are responsible for actioning.
Ok there is one way to do this hopfully I can make it clear and you have the programs.
First the admin must have Infopath. Create a new form with the following data fields
- Date payment received
- Payment no.
- Payee
- Currency
- Amount
Publish it to a sharepoint form libary.
In the form libary add a column for "Who is reponsible"
Go to permissions and make user only able to edit items, (Remove the ability to add items, and remove manage views)
Got to views and within each view remove all execpt for the above fields and who.
Create a default view of datasheet view and again make sure to only have the above fields.
Now that this does is that the admin will have the infopath form and can add items to the list. When the items are displayed in the list users will not be able to change the contents of the cell, (only way to do that is to open the infopath form which they will not have installed on their computer or you remove the links from the views) And have the one added field of "Who" the user will be able to change it from the datasheet view.
This is not a fullproof solution but its the closest I can get. It took me about 1/2 hour to setup on a test machine.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.