-
What about creating a new form, and a new library, and seeing if it happens again?
I don't think reinstalling InfoPath will solve this.
-
Whoo hoo! Teamwork for the win, glad you have it working!
-
I have 2 forms used for tracking calls and resolving issues. The first is called "Tier 2" - this is the rep who answers the call and fills in basic information. Tier 3 can be assigned an issue resulting from this call. In their form, I want them to be able to enter or select an ID and have this form (the ...
-
Thanks for reply Ernesto,
I can't go with attachments.... just wondering what if it's something in Sharepoint settings, but error message comes from InfoPath. Don't know what to do. Reinstall InfoPath?
-
Hilary, thanks for your time. It was indeed the mapping file. I went back and redid my sample form with the correct mapping to the ID and Attachment fields. It is now working!! :)
thanks
-
So - here's my workaround. Add a field to the main data source. Set its default value to a calculated value - that would be the filtered XPath - MyExternalField[. = UID] or what have you.
Then, in the calculated value I was testing with, I used addDays with my new field (the one with the default value).... does that work in your circumstances?
-
Oh wow - never mind what I just said - while the formula editor is not complaining, my form won't open in preview - when I preview I get the same error you were getting!
-
So, I just tried this - I added a caclulated value on a form, and used addDays with the field I'm adding to from a secondary data connection (a SharePoint list). I added a filter - that another field in my SharePoint list must be equal to a field in my form. I did not get an error from the formula editor. But I think you are saying that your ...
-
(Update: actually the same error occurs with a calculated value box outside of the repeated section as well)
-
There are a couple of relevent factors I should mention.
The formula I am using is for a button label - although the same error occurs for a calculated value box.
Also this is inside of a repeating section bound to a sharepoint list data connection, and when it queries the date field, that's from a different sharepoint list data connection.