InfoPath Dev

This solution works perfectly for me when I preview the form.  When I publish the form as a web enabled form I receive the following error message:  An error occurred while trying to connect to a Web service.

Why will it work as a preview but not once published?

Hi all,

I'm trying to get my infopath form to update current entries in a SP task list.

I'm quite new to this and am struggling to understand a lot of whats being described, however I've got my form to talk to the task list without any errors, but it only submits a blank row of data, nothing else.

I'd really like to have the control of updating data already held within the task list through my form so work can be allocated to different people 'en masse' rather than one at a time.

I've attached my basic example as it is and I've just been trying to update the title, that's all but it just submits a new row every time, can anyone help please I'm pulling my hair out with it?

My CAML code is below

<?xml version="1.0" encoding="UTF-8"?>
<Batch OnError="Continue">
    <Method ID="1" Cmd="Update">
    <Field Name='Title'>0</Field>
        <Field Name='Status'>0</Field>
        <Field Name='ID'>0</Field>
        <Field Name='Due Date'>0</Field>
    </Method>
</Batch>

Blake

 Hey guys,

i have this issue right now, can someone explain what must be changed in order to set the field value to Field[@Name = "Title"]. With the description mentioned to go to the template source file and change SOMETHING does not really help.

Thanks is advance for your assistance.

nedaJav:

Hi How can I publish the form and use it in browser I have published it I get error The form cannot be submitted because of an error. windows 5567

 

Did you figure out this issue? I am having the same problem!

Hi forum members:

I've been reading posts here for quite a while looking for solutions to InfoPath related problems. I have found so many answers here.

I am wondering if the CAML method for submitting repeating table lines to a SharePoint list discussed in depth here works for browser-enabled forms. Our SharePoint is under the Foundation licence so I can't test my forms as browser-enabled. Shortly, the Enterprise licence will be here and I have been wanting to use that publishing method because I am getting problems disseminating my forms. When the respondents try to open the form as an email attachment or in a form library trying "add document" (this often does not work, perhaps on the first try, but after that it works), but alas I have a request to implement the tool I'm designing almost immediately after the Enterprise licence will be ready.

Does anyone know the answer? How about what is the problem for disseminating the forms to the respondents. What could I be doing wrong?

Thanks!

Hello Hillary, I've tried my best to mimic the guidance, but I'm running into problems with understanding how to manage my manifest file to construct the special rules on the SubmittID field. I've attach the .xsn file to assist with your guidance. Thanks, Chris

After our company upgraded the Sharepoint licenses and the infopath browser-enabled forms could function I worked for ages on my form. The question was, will this technique work with forms rendered in the browser.

 The answer: problems were numerous.

The browser forms would give errors based on filtering the target of a rule, a step needed to set the submitted data fields, Field[@Name...]. But the error only occured sometimes. Testing for the cause was tough: I think, [1] once the error occurs, then it will always occur; [2] I believed it worked provided the form template was saved with no filtered targets. This can be seen by selecting the Rule Inspector. If there are targets with filters, it does not recognize them and shows rule as invalid. So if I remove the filters, save the form as [new title], close and reopen in desing, then the Rule inspector gives no errors. Then I would re-hack the manifest file (by the way I used a shorter way to filter the target here by using Field[1], Field[2], Field[3], etc., you don't need to put the [@Name=&quot;Title&quot;] for the @Name="Title", if Title is the first field in the xml file, it can be referenced using Field[1], but this is still a manifest hack) Then immediately publish and the form rendered in the browser would submit the multiple lines to the SharePoint List.

Another issue was the 16 rule recursion threshold, but I couldn't spare the time to test if it would fail in a browser-form. I thought one test I tried showed that the method to bypass the rule does not work on a browser-form.

Bringing me to my last point: the Server maximum operations was the final straw. That was too much and I made one form browser-enabled to utilize some specific benefits (input parameter from a WebPart) but the form I was making that submits many lines to a SharePoint list was made so it could render in a browser with the input parameter (supplied in URL query) but the user was instructed to click a link that opens the form in the client application, and instructions provided to select the single entry from a dropdown that matches the input parameter that they saw on the browser page. No problems if it is a client-opened form: rules, repeating tables, all that stuff.

 Great post Amieqq

Hello,

Could you explain in more detail the duplicate preventing mechanism?

I would really like to implement it in my form.

Thakns,

Darek 

bwhite05:

Yes, I have done that! I have it working for the Update, New and Delete methodologies - it's quite wonderful.

Can you explain how you were able to get updates and deletes working? Thanks.

Hi Hilary, does one have to have VS to adjust the manifest file? Really struggling to get this working especially where setting the field names is concerned (e.g. Field[@Name = "Title"] = Title), no matter what I do it does not allow me to set it like that... I believe I am close but it is the major stumbling block I am facing, I have tried to manually adjust the manifest file using notepad but to no avail, what am I missing? Please can you help me? Thanks, Billy

Hi all,

I wanted to reply to this in case anyone trying to get this to work hits a similar brick wall.

I had set up all the rules successfully and it appeared as though the rules were firing off but nothing was being added to the SharePoint list.

Once you set up a Secondary Data Source pointing to your SharePoint list that you want to submit the records into, go to the Fields panel and use the drop down to select your SharePoint list data source. Browse down to the individual fields and hover over the field names. While some of the fields will be OK, InfoPath will have a different name for the field than it displays as. For example, I added "UniqueID" to my SharePoint list, but after refreshing my data source to include the new column, when I hover over the UniqueID field it shows "UniqueID [UniqueID0]" -- I have to use "UniqueID0" in the Add List Item Template.xml file AND when editing manifest.xml. If I tried just using "UniqueID" it wouldn't work.

To make this whole task easier, I think it would be beneficial if you perform the MSDN steps in this order:

1. Create your list in SharePoint
2. Go to InfoPath and set up a Receive data source to pull the data from your SharePoint list
3. Prepare your 'Add List Item Template.xml' file, but instead of manually typing in the name of each field, go to InfoPath, right click each field in the Fields panel and select "Copy XPath" - Return to your .xml file you're setting up, paste the XPath into the "Field" and then delete everything until you just have the field name. This will ensure the field in your XML file matches the name InfoPath recognizes it as.
4. Do necessary steps to add the rules to your Trigger field, but when you go to edit your manifest.xml make sure you use the same field names as you used in your Add List Item Template.xml file.
5. ????
6. Profit

wsinclair:

Hi Hilary, does one have to have VS to adjust the manifest file? Really struggling to get this working especially where setting the field names is concerned (e.g. Field[@Name = "Title"] = Title), no matter what I do it does not allow me to set it like that... I believe I am close but it is the major stumbling block I am facing, I have tried to manually adjust the manifest file using notepad but to no avail, what am I missing? Please can you help me? Thanks, Billy

You do not need VS to edit the manifest file. If you follow the steps to "Export as Source" so you have the manifest.xml file in a folder with the rest of the source files, you can use any text editor to edit the manifest.xml file. I personally recommend Notepad++ but any "advanced" text editor should work great. "Basic" text editors like Windows' standard "notepad" sometimes doesn't recognize line spacing and it will be one big jumbled paragraph which is why I recommend a more advanced text editor like notepad++.

 I have created a form with add/update functions.  Please take a look, and feel free to update and improve.

castott:

 I have created a form with add/update functions.  Please take a look, and feel free to update and improve.

Hi, I downloaded your form and looks awesome. I have updated with my schema, guid and sharepoint list. Form is submitting, however it does not update list items and cannot work out the reason for your tns:listName been set to my:ListGuid, I thought it should be linked to the data connection Field ListName? Is it working for you? " "