Comments on: Programmatically creating Variation Hierarchies in SharePoint 2007

By: Waldek Mastykarz

Waldek Mastykarz — Mon, 15 Mar 2010 14:12:56 +0000

@Jayasmita: You would probably have to do this manually in code. You would have to delete both the site and the Variation Label. Please note that you can delete only non-root Variation Labels.

By: Jayasmita

Jayasmita — Mon, 15 Mar 2010 12:50:09 +0000

I have tried this and it works fine. Variation Site and labels gets created and heirarchy is setup properly on feature activation but I don't find the way to delete the variation site on deactivation. Anyone's help is appreciated. Thanks.

By: Waldek Mastykarz

Waldek Mastykarz — Mon, 02 Feb 2009 19:23:00 +0000

@Hardy: you've just done it yourself. Your comments might save a few SharePoint environments out there.
Thank you for your feedback.

By: Hardy

Hardy — Mon, 02 Feb 2009 19:19:43 +0000

The customer is also getting the error when using the STSADM command. And as soon as we disable the feature and create the variations manually this error does not happen. But we will try it at the system of the customer if there might be something else.

Still you should write in your post that this is not supported (even if it is a really good idea) – this helps some customers to not getting in troubles.

By: Waldek Mastykarz

Waldek Mastykarz — Mon, 02 Feb 2009 17:46:19 +0000

@Hardy: Unfortunately, I haven't used it in combination with the export API myself. Are you getting the problem only while creating Variations programmatically or while using Variation in general?

By: Hardy

Hardy — Mon, 02 Feb 2009 12:25:37 +0000

I have a small question. A customer has tried this – and it seems to work. But after activating this feature a export of the site collection using stsadm or using the deployment API is not possible anymore (Problems when creating the web structure). Have you tried this or could you try this and tell me if this does work on your machine?

And of course – this is definitly unsupported – I would never do that in a production environment. And I agree with Spence – this is a license violaton. I would never recommend this to a customer. Neverless – I also agree that the functionality should be available from the API.

By: Waldek Mastykarz

Waldek Mastykarz — Fri, 02 Jan 2009 07:56:10 +0000

@Spence: That's what I was afraid of. Well, hopefully the MOSS team will 'fix' it in vNext ;)

By: Spence

Spence — Fri, 02 Jan 2009 03:54:30 +0000

This is 100% unsupported and indeed a license violation. Doesn't mean it isn't a good idea :). Variations should be 100% programmable if this feature is to be a true platform for multi-variations.