修改manifest.xsf后将Infopath Forms发布到其他env时出错 [英] Error when publishing Infopath Forms to other env after modifying the manifest.xsf

查看:70
本文介绍了修改manifest.xsf后将Infopath Forms发布到其他env时出错的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好。


我对SharePoint 2010中的Infopath表单有疑问,只是为了解释这种情况:

我创建了一个列出infopath表单,我想在其他环境中使用这些表单,如test等,因为表单很难耦合到列表我不能只将它们安装到另一个环境。研究Google向我展示了我可以使用新的URL,ListID和ContentTypeID修改xsn中的manifest.xsf
文件,创建一个cab并使用Infopath Designer发布它。


我已经做了所有这些,它似乎是正确的但是当我尝试使用Infopath Designer发布时我得到一个错误说:


类型 'Microsoft.SharePoint.SoapServer.SoapServerException' 引发的异常<细节>< Errorstring,则的xmlns = QUOT; HTTP://schemas.microsoft.com/sharepoint/soap/">价值不在预期范围内。< / errorstring>< / detail>




<我已经检查了日志,我在其中看到以下内容:
$
ConstructFromXsnFile因未处理的异常而失败System.ArgumentException:值不在预期范围内。   ;&NBSP;


  at Microsoft.SharePoint.SPContentTypeId..ctor(String id)   


  at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.Parse(XPathNavigator dataAdapterNode,XPathNavigator serverConfigNode,XmlNamespaceManager solutionNamespaceManager,Solution solution)  &NBSP;&NBSP;


  at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapter.CreateDataAdapter(XPathNavigator dataAdapterNode,XPathNavigator serverConfigNode,XmlNamespaceManager solutionNamespaceManager,Solution solution,CreateAdapterMode mode )&NBSP;&NBSP;&NBSP;


&NBSP;在Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapters.Microsoft.Office.InfoPath.Server.SolutionLifetime.ISolutionComponent.Parse(的XPathNavigator documentClassNode ,XmlNamespaceManager solutionNamespaceManager,ConversionContext context)   


  at Microsoft.Office.InfoPath.Server.SolutionLifetime.Solution.ParseManifest(ConversionContext context,XPathNavigator node)   


&NBSP;在Microsoft.Office.InfoPath.Server.SolutionLifetime.Solution.LoadFromXsn(ConversionContext上下文,SolutionCabinet solutionCabinet,SolutionIdentity solutionId)&NBSP;&NBSP;&NBSP ;


&NBSP;在Microsoft.Office.InfoPath.Server.SolutionLifetime.Solution<> c__DisplayClass2< ConstructFromXsnFile> b__0()&NBSP;&NBSP ;&NBSP;


  at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException,TryBlock tryBlock,FilterBlock filter,CatchBlock catchBlock,FinallyBlock finallyBlock)

 

部署失败转换,或设计检查程序发现致命错误:验证表单模板时发生意外错误。


  

 我没有更改模板上的任何内容,只更改了URL /列表ID和ContentTypeID的值,


 这些我已更改的部分清单:


 < xsf3:solutionDefinition>

 < ; xsf3:viewsExtension>

&NBSP;&NBSP;< xsf3:viewExtension REF ="编辑项目">< / xsf3:viewExtension> <登记/>
&NBSP;< / xsf3:viewsExtension>

&NBSP;< xsf3:的baseUrl relativeUrlBase = QUOT; < a href ="http:// sp2010 / TestSite / ListItems / ListItem /%22 /"> http:// sp2010 / TestSite / ListItems / ListItem /" / >

< / xsf3:solutionDefinition>



< xsf:query>

 < xsf:sharepointListAdapterRW queryAllowed =" yes" submitAllowed = QUOT;是" SITEURL = QUOT; ../../& QUOT; sharePointListID = QUOT; {B03A676F-780D-49F7-B9CA-0FDD4FFB8CDR}" name =" Main Data Connection" contentTypeID = QUOT; 0X0100068ECFE0863EFF45A9B7ECB118B5EFA700205EF8DA3DFCF34AB31EA5C2A6B923BG"
relativeListUrl =" ../& quot;版本= QUOT; dc19d1e732d326f4" queryOneItemOnly =" yes">






任何人都遇到过这个问题?

你如何解决它?


许多资源都解释了这种方法,所以我认为现在应该可行了。我很好奇为什么它对我不起作用。




解决方案

你好Alnedru,


有关于此的博客类似主题,请再次测试:


https://www.c5insight.com/Resources/Blog/tabid/148/entryid/ 613 / how-to-migrate-a-sharepoint-2010-infopath-list-form-to-sharepoint-2013-or-sharepoint-online.aspx


谢谢,


Wendy


Hello everyone

I have a question regarding the Infopath forms in SharePoint 2010, just to explain the situation:
I've created a list infopath forms and I would like to use these forms in other environments like test, etc, because the forms are hard coupled to the list I cannot just install them to another envirment. Researching Google showed me that I can modify the manifest.xsf file in xsn with the new URL, ListID and the ContentTypeID, create a cab and publish that with the Infopath Designer.

I have done all of that, it seems to be correct BUT when I try to publish with Infopath Designer I get an error saying:

Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.<detail><errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">Value does not fall within the expected range.</errorstring></detail>


I've checked as well the logs and I see the following in there:
ConstructFromXsnFile failed with unhandled exception System.ArgumentException: Value does not fall within the expected range.   
 at Microsoft.SharePoint.SPContentTypeId..ctor(String id)   
 at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.Parse(XPathNavigator dataAdapterNode, XPathNavigator serverConfigNode, XmlNamespaceManager solutionNamespaceManager, Solution solution)   
 at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapter.CreateDataAdapter(XPathNavigator dataAdapterNode, XPathNavigator serverConfigNode, XmlNamespaceManager solutionNamespaceManager, Solution solution, CreateAdapterMode mode)   
 at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapters.Microsoft.Office.InfoPath.Server.SolutionLifetime.ISolutionComponent.Parse(XPathNavigator documentClassNode, XmlNamespaceManager solutionNamespaceManager, ConversionContext context)   
 at Microsoft.Office.InfoPath.Server.SolutionLifetime.Solution.ParseManifest(ConversionContext context, XPathNavigator node)   
 at Microsoft.Office.InfoPath.Server.SolutionLifetime.Solution.LoadFromXsn(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId)   
 at Microsoft.Office.InfoPath.Server.SolutionLifetime.Solution.<>c__DisplayClass2.<ConstructFromXsnFile>b__0()   
 at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)
 
Deployment failed conversion, or design checker found fatal errors: An unexpected error has occurred while verifying the form template.

  

 I did not change anything on the template, only the values for URL / List ID and ContentTypeID,
 These parts that I have changed in manifest:

 <xsf3:solutionDefinition>
 <xsf3:viewsExtension>
  <xsf3:viewExtension ref="Edit item"></xsf3:viewExtension>
 </xsf3:viewsExtension>
 <xsf3:baseUrl relativeUrlBase="http://sp2010/TestSite/ListItems/ListItem/"/>
</xsf3:solutionDefinition>

<xsf:query>
 <xsf:sharepointListAdapterRW queryAllowed="yes" submitAllowed="yes" siteURL="../../" sharePointListID="{B03A676F-780D-49F7-B9CA-0FDD4FFB8CDR}" name="Main Data Connection" contentTypeID="0X0100068ECFE0863EFF45A9B7ECB118B5EFA700205EF8DA3DFCF34AB31EA5C2A6B923BG" relativeListUrl="../" version="dc19d1e732d326f4" queryOneItemOnly="yes">



Anyone did come across this issue?
And how do you resolve it?

Many resources explained about this approach so I suppose it should work now I'm curios why it doesn't work for me.


解决方案

Hi Alnedru,

There is a blog about this similar topic, please test again as it:

https://www.c5insight.com/Resources/Blog/tabid/148/entryid/613/how-to-migrate-a-sharepoint-2010-infopath-list-form-to-sharepoint-2013-or-sharepoint-online.aspx

Thanks,

Wendy


这篇关于修改manifest.xsf后将Infopath Forms发布到其他env时出错的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆