View Complete Post
I have built a project intake form in InfoPath and am submitting it to SharePoint. Part of the form uses the Person/Group Picker control. I wish to publish that field to SharePoint upon form submission. However, the column title is "Display
Name." Is there anyway I can change the name of that? I tried editing the list in SharePoint and that field is not editable. I also tried renaming the field in InfoPath, but it is part of the Person/Group Picker control, is a locked
field, and will not let me change the InfoPath given name. I also looked at changing the name of the field during the publishing wizard process, but it will not let me do so there either.
Am I just stuck with that name if I want to use the Person/Group Picker control?
I am using InfoPath Designer 2010 and I believe SharePoint 2010 (although it may be MOSS 2007).
Custom field types provide a powerful way to define a reusable SharePoint column definitions.
MSDN Magazine May 2009
I have an InfoPath web-enabled form in MOSS 2007, that is integrated with a K2 blackpoint process for an approval workflow.
Once the form (a Purchase Order request form) has been approved in the K2 workflow process, I switch the form view to a "print-friendly" view for the requestor to view from the browser. However, now I need to go one step further with this scenario:
1) I need to somehow insert/embed an image with the scanned-in signature of the approver (likely stored in a SP doc library) at the signature line section of my form. Also, what are the security requirements for storing such images, but not granting
all users access to these (e.g. only services accounts that need to access this for embedding into the form, etc.)?
2) Then I need to convert this final "print-friendly" view of the form (with the signature image) to a PDF document so that I can store it in SharePoint (and email it to the requestor using K2's email event capabilities).
Can anyone help me with a solution to both of these requirement, or point me to some resources for this (even 3rd party components are open-game).
I'm in the process of migrating from a WSS 2 site to WSS 3/MOSS. On the old site I used an Infopath 2003 form for absence requests. During the migration I now use Infopath 2007. There wasn't any problem initially when the form was stored with the SharePoint form library. However, when I published the form as a content type from Infopath 2007 and then added that content type to the form library, there are two columns for each piece of data from the form. (One from the content type and one from the form list.) I relinked each old form (list content type) to the new AbsenceRequest content type and removed the original one from the list. However, the duplicate column names are still there. Since they came from the Infopath form, they are not editable or deletable from the SharePoint list management interface. The duplicate column names make it tough to build views since it isn't apparent which column to use in the form building UI. It can be determined form the overview display, but it is very cumbersome.
Does anyone know a way to get rid of the old, absolute, columns?
I have a document library with the standard name column linking to the document. However, we'd like to create a custom field and have that link to the document (and edit item menu).
How is this best accomplished?
Thanks in advance!
I have a sharepoint list[Managers] with groupby sector column. like below
Each Sector group by column data i want to display in label or panel control.
How to do that ? how to write the logic?
I am making use of SharePoint List Batch Updating methodology in order to update the items in bulk. I build the query dynamically for each and every item using StringBuilder and process the data ultimately using 'ProcessBatchData' Method.
Now, I have a requirement where I have to increment a particular field value in the query while iterating through each item for building the query. How can I auto-increment a field value for each item in the batch query?
I found many examples such as this which is completely wrong. In the example below the [Today] is only calculated on item creation and edit, not every time list item is accessed.
This is very important my customer wants it done asap.