InfoPath Dev

Sorry Hilary, I'd like to send it to get to the bottom of this, but I don't think I'm allowed to send out some of the information in this form. I think I'm looking at just going back to a working version and building it back from there. What I'd like to know is why this might happen, i.e. if there are constaints on the ...

I have designed a form from an existing sharepoint list (named "1Q documents"), now I want to use that form for a separate list ("2Q documents") that has the same columns, but different row data. I'm new fairly new to sharepoint, and really new to InfoPath. Can this be done? Am I missing something?

I'm getting an error in the Qdabra Event Log on the DBXL server below:  Url: /QdabraWebService/DbxlDocumentService.asmx System.ArgumentException: Unsupported property type: long at Qdabra.Dbxl.Domain.Document.PopulateProperties() Can someone point me in the right direction on where to look to clean up this error. The form ...

 The result node in the QdabraRules data source will contain a string with a little sentence like this: Item 89 does not match. For each non matching item. The comparison is done only based on the qRulesLastModified attribute as compared to the last modified date time in the list. If no values in the list item were changed except the ...

Thank you Hilary, I was thinking to use "delimited list" as I think the "result" returns a simplified repeating list, but was not sure whether the result's formatting is changing with the type of modifications. If I understand correctly the standard behavior  of RefreshSharepointList using the attribute is to check ...

 Hi - Refresh with the mode of Report will only let you know if there are diffs and create a list of data to allow qRules to know what to delete the next time you submit (if you have deleted items from the XML). Adding the qRulesLastModified attribute won't require you to remap anything. The results node in the QdabraRules data ...

 Hi Doreen, DBXL currently does not have this feature, but I'll add a request to consider this as an enhancement. Thank you.

 For me it's not the content of the form. It's the constant saving, changing, moving and publishing that I think breaks the design of the form.

I have an issue where a client has a Form Library that has over 1000 existing Infopath forms.  The client has requested a new field be added to the form that will be published to the Library.  This field is a calculation based on other fields within the form.  My issue is that on new forms or any form that is opened and submitted, ...

I've not run into this before - any chance you'd email me a copy of the form so I could see the issue & see if it repros for me?