-
So this is a bit of a strange one and I cannot seem to figure it out; I should preface that I'm fairly new to InfoPath.
I have a form with a repeating table that is pulling data from a secondary source. In order to grab the appropriate data I have added a field called "counter" with the default value of: ...
-
has anyone seen this/ know a workaround to fix it?
I have infopath forms defined for display, edit, and new.
I have defined the view on the list for each to point to the appropriate form.
when I go to the list, I see the correct form for the correct function.
however, when a general user goes to the site, and when some other admins go ...
-
We are experiencing this same issue with a form and cannot get it to display consistently between computers. Anyone solve this yet?
-
This seemed to resolve the issue:
$f = Get-SPInfoPathFormsService
$f.Properties.Add("AllowEventPropagation", $false)
$f.Update()
Reference link: https://support.microsoft.com/en-us/help/2984138/forms-timeout-or-take-a-long-time-to-open-in-infopath-2010-or-infopath
-
So - this sort of depends on the details. Do you mean you need the labels in Spanish instead of English? Or you need to give the user a choice of language? We oftentimes use XML data sources for translations - you can store the label values in the various languages you want, then add some logic to display the right one. I'm attaching a simple ...
-
Tricky. That's because this is a multi-select, I think. See the attached screenshot - when you create your formatting condition, you likely need to display the advanced view for the data source, then select all instances.
-
You could maybe have a single doc library these submit to and promote a field indicating where you'd like them to go - then use workflow to move them to the correct library.
-
Ah, I think we dealt with this one via email - sorry I'd missed this original post! - the issue was the namespace in the XSLT - the namespace for the "my" prefix changed from one template to another (expected) so the XSLT needed to be updated to reflect that.
-
It would be great to actualy fix the issue, but I'd be willing to recreate the whole form if I could.
Currently cannot publish, throws a SOAP message cannot parse error.
So, how would I give myself a do-over where the manifest and connection will be re-written.
So... is it an issue of deleting the xxxifs.aspx forms in SPD?
-
Hi Hilary,
Thanks for coming back to me over this one - I did think it unlikely that there was a 'simple' solution, or in fact much of a solution at all as I've hunted hard to see if there was an answer or guidance and I've found nothing. I did read one person who has used a method of splitting the manifest.xsn out ...