Showing posts with label List. Show all posts
Showing posts with label List. Show all posts
Friday, November 14, 2008
Customize list form
This is really still just my own memo.
To redirect after submit, add ?source=URL.
The official way (http://office.microsoft.com/en-us/sharepointdesigner/HA101191111033.aspx) of creating a custom list form, uses the DataFormWebPart.
It has a limitation. Attachment does not work. So it has to be disabled.
There seems unsupported workaround exists. http://cid-6d5649bcab6a7f93.spaces.live.com/blog/cns!6D5649BCAB6A7F93!130.entry
If it is just to apply the coporate masterpage, we could go just by replacing that of the default NewForm.aspx with whichever masterpage we want.
Attachment works.
BTW, NewForm.aspx uses ListFormWebPart. We can not customize it, or a very little. For instance, it seems we can not hide fields that we do not need users to fill in.
Input validation. http://rdacollab.blogspot.com/2007/07/custom-sharepoint-edit-forms-with.html
Wednesday, October 1, 2008
FlexListViewer
http://blogs.infosupport.com/porint/archive/2006/08/15/9865.aspx
Have you ever wanted to have a list presented on a page, which resides in a site different from where you have the list?
I believe the list and view are one of the big selling points of Sharepoint. I like them very much. On the contrary, I do not like the Content Query Web Part. Out of question.
Our site is of multi-lingual. We use the Variations technique. Though there are many points of it that I am not happy. This, I believe is one of the biggest shortcomings.
If you say to your users that they have to manage a separate list for each different language, they would laugh at you.
FlexListViewer is my saviour. It allow to have a view displayed in the other site than the one the list belongs to.
Better even, the source code is available. There was a small point of it that does not really fit to our need. We are in the usual, stagin -> internet facing setting. We prepare pages in the staging, and the Content Deployment pushes them to the internet facing site. The out-of-box FlexListViewer, the view URL needs to be a full URL, starting with http://hostname. But in our case, that changes, in the course of deployment. So, do not want to really specify any host.
Thanks to the developper, who made the source available. I modified it so if the specified URL starts with “/”, it assumes the host it is on.
Have you ever wanted to have a list presented on a page, which resides in a site different from where you have the list?
I believe the list and view are one of the big selling points of Sharepoint. I like them very much. On the contrary, I do not like the Content Query Web Part. Out of question.
Our site is of multi-lingual. We use the Variations technique. Though there are many points of it that I am not happy. This, I believe is one of the biggest shortcomings.
If you say to your users that they have to manage a separate list for each different language, they would laugh at you.
FlexListViewer is my saviour. It allow to have a view displayed in the other site than the one the list belongs to.
Better even, the source code is available. There was a small point of it that does not really fit to our need. We are in the usual, stagin -> internet facing setting. We prepare pages in the staging, and the Content Deployment pushes them to the internet facing site. The out-of-box FlexListViewer, the view URL needs to be a full URL, starting with http://hostname. But in our case, that changes, in the course of deployment. So, do not want to really specify any host.
Thanks to the developper, who made the source available. I modified it so if the specified URL starts with “/”, it assumes the host it is on.
Subscribe to:
Posts (Atom)