The answer might be simple. The first time a column is created and you title it “Column1″ the database records that. If you (or someone else) later changes the column title to “Column2″ your application will break. Why? Because behind the scenes that column is still “Column1″
This was done on a SharePoint Online site.
This was done using a SharePoint Online site.
The following video demonstrates how to add streaming video to a SharePoint Online private site collection.
Please note: this will not work on a SharePoint Online public website
Building forms using SharePoint Designer can be a bit tricky at times. What if you wanted to a text box to show only if a certain radio button value is selected? This video will show you how I acheived this using jQuery.
This post might also help:
Validating a SharePoint form field in SharePoint Designer 2010
Using jQuery to hide form elements based on drop-down value.
This video will demonstrate how to populate a asp.net drop down list control with SharePoint list column values. I’ve created a visual web part in Visual Studio 2010 and used the sever object model to demonstrate this. However, you can populate a drop down list with the client object model if you prefer.
This video will demonstrate how to populate an HTML drop down list control with SharePoint list column values. I’ve created a visual web part in Visual Studio 2010 and used the client object model to demonstrate this. Why would I need to use the client object model? When developing for sandboxed solutions, the whole server object model is not open for use. In some cases, such as developing for SharePoint Online, client object model will be useful if not absolutely necessary. However, you can populate a drop down list with the server object model if you prefer.
- Finds the list “My Tasks”
- Gets all items from the “Title” column in the “My Task” lists
- Uses a foreach loop to add all of the “Title” columns values to a drop-down.
Watch the video to see how it works.
InfoPath 2010 repeating tables are useful and sometimes even essential to the project requirements. However, they carry with them some problems. For one thing when multiple values are entered into an InfoPath 2010 form all of the values become crammed into one SharePoint 2010 column. This will cause all kinds of problem down the road if you ever need to access that Info and/or filter it etc. So the following example shows how to move the repeating table values to a separate list where the values can be more efficiently managed.
- I’ve created a Visual Studio 2010 visual web part that fires the code on page load
- You must have a delimiter to separate the values. In this case I have used a ;
- Do NOT add a ; to the last repeating table entry. If you do you will have and extra record in the new list.
How does it work? View the Video below: