Publishing page layout
- Hi,
We have a requirement where we have a form to be filled. The approach that we are using is to create site column and content types using sharepoint API and installing it as a feature. Now we are designing a layout page where we are using the content type created earlier.
Now the requirement is that we have to enter the detail of speakers and the number of speakers is to be decided at runtime. Now in speaker detail we have three fields :
1. Speaker name
2. Description
3. Image
Now these are the details of one speaker. In the same way we can have n number of speakers and number of speakers is to be decided at run time.
I am having difficulty in deciding how to implement it. I have few questionas regarding same:
1. Can we have repeating column.
2. Can we use two content types for the same layout page.
3. Any other approach.
Please help with this issue.
Prachi
Answers
I don't quite understand your requirement, so let me give you a couple options:
1.) If what you want is some sort of aggregated list of speakers, what you should do is create one publishing page for each speaker, then you have a "roll up" page where you use the Content Query Web Part to display information from all the speaker pages in one view. If you don't want all the Speaker publishng pages to be displayed in your Content Query Web Part, you can add a column to your Speaker Publihing Page where page authors can specify which view this speaker should show up in, then you can filter by that custom column in the Content Query Web Part so only Speakers with that column value appear in your aggregated list.
2.) If you really want users to be able to add multiple speakers to one page, you can look at the possibility of creating a custom field type and custom field control to do that.
Visit my blog at blog.beckybertram.com or follow me on Twitter: @beckybertram- Marked As Answer byLu Zou-MSFTMSFT, ModeratorThursday, October 29, 2009 5:40 AM
Take a look at some of these articles on MSDN:
http://msdn.microsoft.com/en-us/library/ms446361.aspx
http://msdn.microsoft.com/en-us/library/aa981226.aspx
http://msdn.microsoft.com/en-us/magazine/dd727508.aspx
Visit my blog at blog.beckybertram.com or follow me on Twitter: @beckybertram- Marked As Answer byPrachi taunk Thursday, October 29, 2009 7:47 AM
All Replies
I don't quite understand your requirement, so let me give you a couple options:
1.) If what you want is some sort of aggregated list of speakers, what you should do is create one publishing page for each speaker, then you have a "roll up" page where you use the Content Query Web Part to display information from all the speaker pages in one view. If you don't want all the Speaker publishng pages to be displayed in your Content Query Web Part, you can add a column to your Speaker Publihing Page where page authors can specify which view this speaker should show up in, then you can filter by that custom column in the Content Query Web Part so only Speakers with that column value appear in your aggregated list.
2.) If you really want users to be able to add multiple speakers to one page, you can look at the possibility of creating a custom field type and custom field control to do that.
Visit my blog at blog.beckybertram.com or follow me on Twitter: @beckybertram- Marked As Answer byLu Zou-MSFTMSFT, ModeratorThursday, October 29, 2009 5:40 AM
- Hi Becky,
Thanks for the reply.
We actually want to use the second option i.e.We really want users to be able to add multiple speakers to one page.
The solution that you are suggesting for it is to look at the possibility of creating a custom field type and custom field control to do that.
can you suggest more on how to achieve that. this is what we want to implement.
Prachi Take a look at some of these articles on MSDN:
http://msdn.microsoft.com/en-us/library/ms446361.aspx
http://msdn.microsoft.com/en-us/library/aa981226.aspx
http://msdn.microsoft.com/en-us/magazine/dd727508.aspx
Visit my blog at blog.beckybertram.com or follow me on Twitter: @beckybertram- Marked As Answer byPrachi taunk Thursday, October 29, 2009 7:47 AM
- Hi Becky,
Thanks for the reply.
We are able to run the sample code and this is what we wanted to do.
Now we are trying to implement it according to our requirement.
Prachi
