Question

I would like to know if there is a way to deploy (or migrate) an XsltListViewWebPart with a content deployment job ?

To explain further, I have two environments, "Authoring" and "Production", and I create the list view webparts using the well-know export process (SPD, "export", upload in WP gallery). These webparts are used in the sub-sites to display lists and libraries located at the root site. The thing is that if I don't specify the , I have the "list does not exist" error message, but then, it does not work in the destination site. On the other end, the Destination site has to be created beforehand in order to create the content deployment path. Therefore, the site GUID will be different and if I want my webparts to work on the destination site, I have to adapt the tag before running the deployment job. And I would like to avoid the creation of webparts specific to the "Production" in the "Authoring" one.

Additionally, I played long time with the different elements of the .webpart file, , and , but none of the combination worked.

So, is there a way to solve this problem, creating a XsltListViewWebPart on an environment and using the content deployment jobs for the migration to another environment ?

Any suggestions would be much appreciated.

Best Regards Yves

Was it helpful?

Solution

I suggest you follow the instructions in the post below, which describes the process for deploying the data view webpart in 2007 (same problem, slightly different control).

You can also see within the members of the XsltListViewWebPart that it has the same ListName property described in post (distinct from the GUID)

Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top