Is there any way I can do this?

SharePoint forms library has a custom form template that has a bunch of fields promoted that can be filled in by infopathbut all items in the site have a "Title" column, I cannot seem to figure out how to modify this from within InfoPath.

I tried creating a "Title" field in InfoPath, to see if it would map with the same name, but this just created ANOTHER Title field... that is not a site column.

I seem to have to fill in the form, submit it, then "edit item" and then I can change the title... any help? - sure I'm noJedibut that's no reason to stop trying to make stuff levitat

Hi noJedi- not sure how you're going about this, but you can change the title field in InfoPath by using a rule. What exactly are you trying to do?

Hi Cameron,

I've got a form with defined and promoted fields for use within the form. but there are also fields (like created (date) and modified (date) and created by/modified by for examples only) that I can "Retrieve" data from sharepoint list, but if I have a column (site or just "list column") these things can be seen if you "View/Edit" the item in sharepoint but I can't seem to see any way to have something like a two way binding or a second data source to submit for "columsn"(SP) rather than "fields"(forms xml file)...

Not really sure what I'm asking makes sense to be honest.

Or if this is just "wrong thinking" for sharepoint form/workflow creation...

What I (think I) want to be able to do is from the form/rules:

• to alter workflow settings (approve/reject/cancel/other)
• to see and modify things that are only visible in the "item/edit view" and not the FORM views... modify type columns - eg: "choice" or people - since they provide inherent validation lookups, and ensure workflow values are valid when you are developing workflows also

if you "refresh fields" it brings in a lot of information from the list, destroying the customisation or addition ability for the main datasource (ns1:thing - ns2:myfields - and so on) - this Might be the way to go, but I notice that you don't get everything with this approach...

Couple things to mull over- the created, modified, etc. fields can't be messed with. Also, workflows and InfoPath are two different birds. You can have rules to set a field's value, validate a field, etc. when InfoPath is open, but any other changes at any other time are done through SP workflows. Hope that helps.

Yeah, okay Created/Modified are probably special (and therefore a bad example) but I was just trying to give an example of a field that is IN (all?) lists and libraries (because its a site column?) don't want to modify them (create/mod), but others yes- ie ones we've created... perhaps this is why they don't show up in the "refreshed" fields... perhaps only modifyable fields show up there?

Anyway, I can CREATE a secondary connection "read" from the same list - to get created/modified (for display purposes), so I was just wondering if there is a way to do this...

Failing that I do understand the differences between the "behaviour" or "restrictions" of InfoPath rules and workflow steps, but I am struggling to grok the whys and wherefores around how to manipulate one from the other and keep things in sync.

eg:

form is filled in by InfoPath by user (InfoPath)

approval notifications is send from item creation in list/library(workflow - "on create")

user must use the form to review and "approve/reject" the form, so how do you put a button in the InfoPath to allow an approval to be completed?

(FYI I have put in a very hacky temp workflow that appears to do the job (the workflow looks to promoted InfoPath fields for "step indicators", but I thought it would be much easier to use the "approval workflow" but force the use to review the document in InfoPath... otherwise its easy for the InfoPath to set data and rules that also need to be either worked around or duplicated/syncd in the workflow...)

From everything I've read the "process" needs to go like this:

notification "you have been assigned an approval task" -> open in SP or outlook

user is presented "name/date/comment/approve/reject (and more - reassign, etc)"

but user still needs to also open the item (InfoPath) close the item and find the approval and approve it...

this is a clunky workflow my users are unhappy with, so adding an approval button (and comments field) into the InfoPath form makes sense, but is more difficult than I could easily figure out...

This is where I'm coming from with this line of questi

Yeah, okay Created/Modified are probably special (and therefore a bad example) but I was just trying to give an example of a field that is IN (all?) lists and libraries (because its a site column?) don't want to modify them (create/mod), but others yes- ie ones we've created... perhaps this is why they don't show up in the "refreshed" fields... perhaps only modifyable fields show up there?

Anyway, I can CREATE a secondary connection "read" from the same list - to get created/modified (for display purposes), so I was just wondering if there is a way to do this...

>> Create form -> publish -> Add Site Column "Bob" -> Modify Form to handle bob

Failing that I do understand the differences between the "behaviour" or "restrictions" of InfoPath rules and workflow steps, but I am struggling to grok the whys and wherefores around how to manipulate one from the other and keep things in sync.

eg:

form is filled in by InfoPath by user (InfoPath)

approval notifications is send from item creation in list/library(workflow - "on create")

user must use the form to review and "approve/reject" the form, so how do you put a button in the InfoPath to allow an approval to be completed?

(FYI I have put in a very hacky temp workflow that appears to do the job (the workflow looks to promoted InfoPath fields for "step indicators", but I thought it would be much easier to use the "approval workflow" but force the use to review the document in InfoPath... otherwise its easy for the InfoPath to set data and rules that also need to be either worked around or duplicated/syncd in the workflow...)

From everything I've read the "process" needs to go like this:

notification "you have been assigned an approval task" -> open in SP or outlook

user is presented "name/date/comment/approve/reject (and more - reassign, etc)"

but user still needs to also open the item (InfoPath) close the item and find the approval and approve it...

this is a clunky workflow my users are unhappy with, so adding an approval button (and comments field) into the InfoPath form makes sense, but is more difficult than I could easily figure out...

This is where I'm coming from with this line of questi

What you're describing is how it works. The only way to get around it is to have approve/reject fields in InfoPath, which could be populated by approve/reject buttons that set the field's value. Then have a workflow so that if field=approved, set the status column as approved... etc.

cool thanks for clarifying.