Hi There,
I'm new here - a colleague pointed me over after having some of his issues solved through here.
I have had a look using search and can't see anything quite like my issue, so here goes:
We have a SharePoint 'Task' list. We have altered the standard submission form in Infopath to include additional data fields, and have made it so that the form will allow us to submit multiple tasks to the same list from one from.
We are a university and we are trying to use this to create a list of enhancements for University Programmes and the Modules that make up those programmes.
So, we have used the altered form for programmes, and have created a second task form, aimed at Modules, and published it as a content type to the same Task list.
The standard columns made by the Task form are collecting the field data perfectly, for example, the '% complete' field gathers data into the same '% complete' column regardless of whether we use the 'Programme Task' form, or the 'Module Task' form.
However, the new fields we created on the 'Programme Form', such as 'College' and 'Department', and which we created identically with the same names on the 'Module Task' form, have resulted in duplicate columns on the SharePoint task list. So that if you configure a view you can see 'College' and 'Department; columns twice - once for each form.
We don't know how to solve this, and make the 'College' and 'Department' fields in the two forms point to a single column. We have noticed that when we look at the field properties on the 'Module task' form, a '0' has been added to the field name after publishing.
I had read that you could alter the column destination for the field date by opening the 'Manifest' file, but when i open it up, i cannot see any field or column IDs that i can amend.
Any help on this would be greatly appreciated.
As a side note, we initially tried to have just one task form, with a header section that existing outside the repeating fields where we could get the user to set whether it was Programme or Module, College, Department etc, and just set associated fields in the repeating section to have the data from these header fields as its default values, thereby saving staff time in keep putting int he same data for every task. This worked, however, once a task had been submitted, if it was viewed or edited, the header fields went blank and wiped all that data from the repeating fields, meaning any updates would corrupt the rows in the task list. A header scratcher that we could not solve - hence our current attempt to run 2 forms on the 'Task' list
Any help gratefully appreciated. I can provide screenshots if needed.
Thanks
Chris