Microsoft InfoPath Bloggers https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/feed.xml Wed, 28 Mar 2018 21:07:33 GMT en-US hourly 1 InfoPath 2013 v/s Outlook 2016 https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/infopath-2013-vs-outlook-2016 Mon, 23 Oct 2017 21:47:43 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=305 InfoPath 2013 used to send email differently with Outlook 2013 and it is not working as expected with Outlook 2016. Below were the scenarios InfoPath 2013 MSI  + Office 2016 Click-To-Run -> Does not works InfoPath 2013 Standalone + Office 2016 MSI -> Works InfoPath 2013 MSI + Office MSI 2016 -> Does not works
**Does not works means, the user no longer will get a small inbuilt window but rather outlook email will open.
Expected Actual This caused lots of concerns for the users like they cannot add a semi-colon before the email address. Also if the user has a data connection which submits xml to the library and then sends email and if during the process if the user decides to cancel the email the xml is still submitted to the library which triggered other workflow issues due to the dependency.

To resolve this issue, you need to download the below patch and update InfoPath 2013

https://support.microsoft.com/en-us/help/3039714/february-9--2016--update-for-infopath-2013-kb3039714
Question: Why should we install this patch as this doesn’t talks about the actual issue?
Answer : When you download and update the InfoPath to a higher patch version it may show the Product version to a higher value, it is does not necessarily updates all the dll’s as we do in SharePoint.
In this specific case when we compared the IPEditor.dll of MSI vs Click-To-Run, the Click-To-Run was higher (15.0.4753.1000) whereas the MSI was (15.0.4569.1503). So by downloading and installing the KB3039714 we updated the IPEditor.dll to a higher version (15.0.4789.1000) which contains all the fixes of Click-To-Run.
 ]]> Issue with "UserProfileService.asmx" in InfoPath with SharePoint 2016 https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/issue-with-userprofileservice-asmx-in-infopath-with-sharepoint-2016 Thu, 21 Sep 2017 16:56:56 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=255 This can happen in following scenario:
  1. When we do not set default account while calling the UPA Service in InfoPath form.
2. When we have different time zone selected for a user at User Profile--> Language and Region-->"Always use my personal settings " And setting a different time zone .     Resolution:  There was  a defect raised for this behaviour and the same has been fixed in 16.0.4661.1000. https://support.microsoft.com/en-us/help/4018293/description-of-the-security-update-for-sharepoint-enterprise-server-20 Published by: Neelesh Rai]]> Unable to create Data connection to a List on a specific site https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/unable-to-create-data-connection-to-a-list-on-a-specific-site Tue, 04 Apr 2017 16:39:51 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=245 Unable to connect to the SharePoint site" The issue behavior was specific to one single site collection level. During our troubleshooting we used Fiddler Trace while creating the data connection and saw that InfoPath makes a call to the lists.asmx and the lists.asmx web service successfully returns all the list and library from that site collection Post that it tries to call the webs.asmx and in the non working site collection instead of going to the root sites _vti/_bin/webs.asmx it was considering the managed path Sites as the root site and was constantly making call to sites/_vti/_bin/webs.asmx. We also noticed another strange difference between working site collection and non working site collection. In the non-working site collection when the web service lists.asmx returns the list and libraries in XML Format, the web view under the Fiddler was blank Whereas the working site collection showed the web view for the xml returned by the lists.asmx successfully. We tried to save the non working site collection lists.asmx result as XML file and when we tried to view in IE. Still the IE showed up blank. So there was surely something wrong in the XML output We used another great tool XML Notepad 2007 download from https://www.microsoft.com/en-in/download/details.aspx?id=7973 When we pasted the XML content inside the above tool, it clearly reported that the xml contained invalid characters. So was our goal was identify the invalid character from the XML nodes We started deleting each node and when we deleted one such node, the error was gone! We found that the node was a library and in the library there was Description field which had some invalid characters Once we deleted the description from the library settings, the lists.asmx returned the xml output which started showing successful web view in the fiddler And InfoPath was able to create the data connection successfully.    ]]> "Unknown network error" on people picker in InfoPath form https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/unknown-network-error-on-people-picker-in-infopath-form Wed, 15 Feb 2017 02:44:51 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=225 Symptom: You get error "Unknown network error" while resolving the user in people picker control in InfoPath filler form at your SharePoint online site. Note: The people picker is working as expected in browser based form. We were able to identify the offending code change and the problematic deployed code has been disabled now. Published by: Neelesh Rai]]> Administrator Approved Forms fails to upload to SharePoint server 2016, if you have "External Item Picker" control added to the Form https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/administrator-approved-forms-fails-to-upload-to-sharepoint-server-2016-if-you-have-external-item-picker-control-added-to-the-form Fri, 03 Feb 2017 19:04:07 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=215
  • Save the admin approved Xsn as Cab File
  • Extract the cab files
  • Modify the view1.xsl (I had just one XSL file. In complex form there might be many depending upon the number of views. So if you have this control on different views then you may need to update all the impacted XSL’s)
  • Search for the below line ( You may need to search for either “entitypicker” or classid="clsid:ad74fc20-e09f-4e47-8a87-1da49930867a")
  • Change classid from

    •                 <object class="xdActiveX" hideFocus="1" style="HEIGHT: 22px; WIDTH: 288px" tabIndex="0" tabStop="true" xd:xctname="entitypicker" xd:CtrlId="CTRL1" xd:server="http://" xd:bindingType="xmlNode" xd:bindingProperty="InfoPathValue"      xd:boundProp="xd:inline" classid="clsid:ad74fc20-e09f-4e47-8a87-1da49930867a" contentEditable="false" xd:binding="my:group">

    1. To below classid
                    <object class="xdActiveX" hideFocus="1" style="HEIGHT: 22px; WIDTH: 288px" tabIndex="0" tabStop="true" xd:xctname="entitypicker" xd:CtrlId="CTRL1" xd:server="http://" xd:bindingType="xmlNode" xd:bindingProperty="InfoPathValue"      xd:boundProp="xd:inline" classid="clsid:AF339C70-E34E-4E03-B08E-42AB89EA2A0E" contentEditable="false" xd:binding="my:group">
    1. Open the manifest.xsf and try to republish as admin approved form and upload the same now to SharePoint Server 2016 successfully
    ]]>         Yet another flavor of using Enum functions https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/yet-another-flavor-of-using-enum-functions Fri, 03 Feb 2017 18:52:27 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=205
  • Remove the claims information and just retain the username mail address
  • If multiple users are added thenn change the semi-colon to a comma separated values
  • And the above 1 and 2 should loop for all the selected users in the picker control
    • For 1 - We used the simple formula of  -> substring-after(*[local-name() = "AccountId"], "i:0#.f|membership|") For 2 - We included eval like -> eval(Person, 'concat(substring-after(*[local-name() = "AccountId"], "i:0#.f|membership|"), ",")') For 3 - We finally double eval like  -> eval(eval(Person, 'concat(substring-after(*[local-name() = "AccountId"], "i:0#.f|membership|"), ",")'), "..") Some of the learnings- Function Local-name() comes handy when we receive errors like "xyz .... does not point to a valid location path of a field or group" Or we can type manually pc:AccountId instead of inserting as a field to avoid the error]]>         InfoPath Error while submitting an existing form, which uses REST web service to load data https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/infopath-error-while-submitting-an-existing-form-which-uses-rest-web-service-to-load-data Mon, 17 Oct 2016 18:28:12 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=185 "InfoPath cannot save the form. The specified location cannot be accessed. Check that the location you entered is correct and that you have appropriate permission." For existing forms we are fetching the data using the REST web service connection and if we disable that, we can submit the form. But if REST web service data connection to retrieve data is enabled, the form does not get submitted. Resolution: This behavior seems known issue and resolved with the hotfix at https://support.microsoft.com/en-in/kb/2479169 To apply this hotfix, you must be running one of the following operating systems:
    • Windows Vista Service Pack 2 (SP2)
    • Windows Server 2008 Service Pack 2 (SP2)
    • Windows 7
    • Windows 7 Service Pack 1 (SP1)
    • Windows Server 2008 R2
    • Windows Server 2008 R2 Service Pack 1 (SP1)
      Published by: Neelesh Singh Rai]]>         While opening an existing/ new InfoPath form, it is getting opened in the Read Only Mode. https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/while-opening-an-existing-new-infopath-form-it-is-getting-opened-in-the-read-only-mode Sat, 10 Sep 2016 02:04:40 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=165 Scenario:   I've published an InfoPath form (Filler Form) on a SharePoint library. While opening an existing/ new form, it is getting opened in the Read Only Mode.   Cause and Solution:   There could be multiple reasons for this. I've came across two scenario.  
    1. A new form/ existing forms are getting opened in Read Only. I looked at the procmon trace and found below trace,
      12:25:09.9318393 AM TMBMSRV.exe 5688 CloseFile C:\Users\Test\AppData\Roaming\Microsoft\Office\Recent\Sharepoint - 2016-07-12 - Test.xml on sharepoint.Test.org.url SUCCESS   12:25:09.9320745 AM INFOPATH.EXE 12384 QueryAttributeTagFile C:\Users\Test\AppData\Roaming\Microsoft\Office\Recent\Sharepoint - 2016-07-12 - Test.xml on sharepoint.Test.org.url SUCCESS Attributes: ANCI, ReparseTag: 0x0   Which means TMBMSRV.exe (Trend Micro Antivirus), is accessing the XML before InfoPath. TMBMSRV.exe was a client side antivirus and removing this antivirus, fixed this issue.    
    1. An existing form is getting opened in Read Only but new one works fine.
      The issue was only on Windows 7 machine and we found Web Client has a limitation of 50 MB. This limit is by default and could be modified, if needed from “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\FileSizeLimitInBytes”.   Posted By: Himanshu Saxena]]>         The form cannot be submitted because some of the e-mail addresses cannot be resolved. If you know the values in the form that specify the e-mail addresses, revise them and try again. https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/the-form-cannot-be-submitted-because-some-of-the-e-mail-addresses-cannot-be-resolved-if-you-know-the-values-in-the-form-that-specify-the-e-mail-addresses-revise-them-and-try-again Sat, 10 Sep 2016 02:03:23 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=155 Scenario:   I've put a people picker in the InfoPath form and pulling emails id to send emails based on the display name, which I've filled in the people picker. While submitting the InfoPath Form, I am getting below error for the user Wehrsdorfer, Al. Error : InfoPath cannot submit the form. An error occurred while the form was being submitted. The form cannot be submitted because some of the e-mail addresses cannot be resolved. If you know the values in the form that specify the e-mail addresses, revise them and try again. The following addresses did not resolve in the To line: Wehrsdorfer, Al The following addresses did not resolve in the Cc line: Wehrsdorfer, Al   Cause:   This issue is due to redundancy of the name, as name could be duplicate in a domain. To verify the same, open outlook and type a name in 'To' now press 'ctrl+k' and it'll suggest you multiple email id's.   Solution:   To remove the redundancy of the name, we started pulling the email id based on the Account Name. As a workaround we've put 'substring-after(AccountID, "\")', which is unique in every domain.   Posted By: Himanshu Saxena]]> Plan to upgrade form templates during an upgrade to SharePoint Server 2010/ 2013 https://docs.microsoft.com/archive/blogs/microsoft_infopath_bloggers/plan-to-upgrade-form-templates-during-an-upgrade-to-sharepoint-server-2010-2013 Sat, 10 Sep 2016 02:02:22 GMT https://blogs.msdn.microsoft.com/microsoft_infopath_bloggers/?p=145 Scenario:   I've migrated the content database from one farm to another and have changed the URL of the site. I have some InfoPath forms in the site collection. To update links that are used in user form templates and data connection files, we need to run the Update-SPInfoPathUserFileUrl cmdlet. (Reference: https://technet.microsoft.com/en-us/library/ee704551.aspx#updateLinks.).   While running the update-SPInfoPathUserFileUrl command, we are getting an exception "The Execute method of job definition Microsoft.SharePoint.Utilities.LinkReplaceTimerJob (ID d15a5af7-539d-43eb-abfd-98100f82b835) threw an exception. More information is included below.  Object reference not set to an instance of an object."   ULS:   When I look at the ULS logs, I see the below stack,   09/02/2016 10:26:32.22        OWSTIMER.EXE (0x0AAC)        0x1B80        SharePoint Foundation        General        8mtf        Medium Processing form template http://sharePoint/MiniProjectsRequests/Forms/template.xsn 369325dd-ac8d-4054-bf44-1c0832046be2   09/02/2016 10:26:33.32        OWSTIMER.EXE (0x0AAC)        0x1B80        SharePoint Foundation        Timer        6398        Critical The Execute method of job definition Microsoft.SharePoint.Utilities.LinkReplaceTimerJob (ID f3e682b4-aad4-47fb-a8a1-187e5a65fd49) threw an exception. More information is included below.  Object reference not set to an instance of an object. 369325dd-ac8d-4054-bf44-1c0832046be2   09/02/2016 10:26:33.32        OWSTIMER.EXE (0x0AAC)        0x1B80        SharePoint Foundation        Timer        72ae        Unexpected Exception stack trace: at Microsoft.SharePoint.Utilities.SharePointLinkReplace.FixXML(Stream fileStream, Boolean fManifest, String filePath, Boolean& fChanged) at Microsoft.SharePoint.Utilities.SharePointLinkReplace.FixXSNBinary(Byte[] originalCabBinary, String fileRelativeUrl, Boolean& fChanged) at Microsoft.SharePoint.Utilities.SharePointLinkReplace.FixXSNFile(SPFile fileTemplate) at Microsoft.SharePoint.Utilities.SharePointLinkReplace.FixList(SPList list) at Microsoft.SharePoint.Utilities.SharePointLinkReplace.ProcessWeb(SPWeb web) at Microsoft.SharePoint.Utilities.SharePointLinkReplace.DoReplaceInternal(SPSite site) at Microsoft.SharePoint.Utilities.LinkReplaceTimerJob.ProcessSite(SPSite site, SPJobState jobState) at Microsoft.SharePoint.Administration.SPAllSitesJobDefinition.Execute(SPContentDatabase contentDatabase, SPJobState jobState) at Microsoft.SharePoint.Utilities.LinkReplaceTimerJob.Execute(SPContentDatabase contentDatabase, SPJobState jobState) at Microsoft.SharePoint.Administration.SPContentDatabaseJobDefinition.Execute(SPJobState jobState) at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) 369325dd-ac8d-4054-bf44-1c0832046be2       Root Cause and Solution:   So basically, we are trying to fix an XML using this command. In this case, I exported the XSN file and found that 'manifest.xsf' was renamed as 'manifest - copy.xsf'. I changed it back to 'manifest.xsf' and able to fix the XSN using the command 'Update-SPInfoPathUserFileUrl'.   Posted By: Himanshu Saxena]]>