I get a weird error message when trying to create new Visual Studio 2010 project of type "SharePoint 2010 Sequential workflow":
"The SharePoint site at "somesite" is missing a target, task, or history list. Each of these lists is required to associate a workflow template. Please create a list and then launch this wizard."
I already have two projects in my Visual Studio 2010 solution: MyListsDef with many SharePoint custom lists defined and MySiteDef with site definition to populate those lists when new SharePoint site is created.
I have to create SharePoint workflow project for some of my lists in Visual Studio 2010.
I made some steps prior creation of third (SharePoint Sequential workflow) project in my solution:
Compile and package both MyListsDef and MySiteDef,
Install both MyListsDef.wsp and MySiteDef.wsp as solutions on my SharePoint 2010 server,
Create new SharePoint 2010 site based on MySiteDef template,
Create new Visual Studio 2010 project "SharePoint 2010 Sequential workflow" with reference to SharePoint site, created in step #3.
However, I always get the error "... is missing a target, task, or history list." every time I select a site, created in step #3, as a reference in a sequential workflow wizard in Visual Studio 2010 in step #4.
What does this error mean and what lists are missing?
What I am doing wrong?
What is a typical way to develop SharePoint workflows with custom lists?
Thanks in advance,
Sal
Sal,
This happens when required lists for workflows are not created.
Do the below to make it work :
ACTIVATE any feature thats relaetd to workflow (1st at SITE COLL level then at WEB level)
Go to the site and select a list
Click on WORKFLOW SETTINGS in the RIBBON
Then ADD A WORKFLOW and then select some workflow (ex: approval)
SAVE it
The above process will create required lists for workflow processing.
Now you can continue with Visual Studio work.
Related
I'm trying to establish whether its possible to connect lists to external SQL tables with SharePoint 2013 Foundation.
I know that is possible in the paid versions through Business Connectivity Services. However, most places I look, BCS is shown as not included in Foundation.
The one thing that contradicts this is page here. Whilst admittedly its titled Office 365, it does include a list for On Premise solutions which suggests that BCS External List IS included in SharePoint Foundation. However, the link takes you to a page entitled “Deploy a Business Connectivity Services cloud-only solution in SharePoint 2013”.
If it is possible, then it seems that we will need to setup a Secure Store to holds ID and passwords for external sources.
Has anyone managed to link Lists to external tables in SharePoint 2013 Foundation (it needs to be 2013 as I understand Microsoft withdrew BCS for that release)? Any pointers would be very welcome to stop us going round in circles.
Thanks,
Chris.
If you have visual studio 2012 installed in the SharePoint server, you can create a "SharePoint 2013 - Empty Project", and then in the project, add a new item called "Business Data Connectivity Model".
You can search for many tutorials for "Business Data Connectivity Model", such as the example link below (note the video is about sharepoint 2010, but you can use it for sharepoint 2013):
http://msdn.microsoft.com/en-us/vstudio/ff623022.aspx
This solution will work for SharePoint 2013 Foundation as I have done that myself.
regards Taz
I'm developing a sequential Sharepoint Foundation (Share point 2010) workflow in Visual Studio.
I can create costume tasks using a CreateTaskWithContentType activity, I need to create custom search control for this task list that meet my business can you please guide me
Thanks
I am looking for a migration tool. We want to upgrade from SharePoint Server 2007 to SharePoint 2010 in a new environment. We need to have functionality to granulary select which content to migrate and eaven select to map to new structure in the new solution.
We want to tag the content migrated.
The migration tools we are considering are AvePoint, Axceler Davinci, Metalogix.
I'm doing migration scenarios for a consultant firm based in Montreal. First of all, I think you have the correct thinking about how you want to get this done. Doing a SharePoint upgrade (database upgrade) usually bring your SharePoint 2007 problems over to SharePoint 2010.
Here's what we usually do :
Define governance for the new SharePoint platform
Define the new Information Architecture
Implement the new Information Architecture (build sites, lists, libraries, etc.)
Migrate the content over
Tools such as Sharegate (www.share-gate.com) can allow you to do some mapping from your old content source over to the new one.
Hopefully, this will help you!
We have designed a custom workflow using Visio 2010. The workflow has been imported into a Sharepoint 2010 Server team site and is attached to a list. The workflow has three "start approval process" which uses the OOTB approval process . When I go to edit the workflow in Sharepoint 2010 Designer, I go through each step customizing it. Everything is working right up until I get to the second "start approval process" (the first "start approval process" allows me to see the entire structure and customize it to my liking). I click on the second one, it opens in another window with more properties, I select "Change the behavior of the overall task process" and there is no logic at all on this approval process, it is completely blank and only has an opening step (start typing or use the insert group in the ribbon).
When I take this same Visio 2010 and import it into a completely different Sharepoint 2010 Server, import it and try the same process, it works fine...I can modify all the approval process points.
I should state the difference between the two is that the one in which everything works, I'm importing and changing as a farm admin (test system). The other Sharepoint server in which it is not working, I definitely do not have full admin.
I'm willing to bet it is a permission issue, if it is, what permission should I grant and why is it working for one but not all?
Strangest thing, as soon as I completely closed Sharepoint Designer and re-opened it again, this issue did not occur!
Lesson learned, don't leave apps open on your desktop so long, Reggie!
How do I change process template to MSF for Agile on an already existing team project in TFS 2010?
We have upgraded our TFS 2008 to 2010, and now I would also like to change the process template to MSF for Agile (currently CMMI).
We haven't used the workitem functionality much so if some information gets lost in the conversion doesn't matter.
Once you've created a Team Project, you unfortunately can't just upload a new process template. As Robaticus says, you'll have to download the XML for the template and modify it, then re-upload it. The power tool lets you create NEW templates for NEW team projects, but it won't modify an existing one.
Instead, you can use the witadmin.exe tool (on any computer with Team Explorer installed, under \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE, or just from a Visual Studio Command Prompt) to export the current workitem definitions and re-import them once you've made your changes.
Luckily, if you're not using workitem tracking much, then this might not be too difficult. You might be able to just delete all the existing workitem types and then re-upload the new types.
If this is too much trouble, consider how much you want to retain your source control history. It might be worth creating a new Team Project with the Agile template and then just moving all your source code into it.
You can't change the process template, however you can change the work item types. So for bugs, tasks you can swap to the Agile definitions.
You can do this in 2010 with witadmin, in 2008 it's importwit, by first downloading the template to disk (you'll need the TFS power tools for this). Then point the console app at bug.xml, task.xml etc..
Usage: witadmin importwitd /collection:collectionurl [/p:project] /f:filename [/e:encoding] [/v]
/collection Specifies the Team Foundation project collection. Use a fully specified URL such as
http://servername:8080/tfs/Collection0.
/p Specifies the team project in which the new work item type is imported. This is required, except when
the validation-only option is used.
/f Specifies the work item type XML definition file to import.
/e Specifies the name of the .NET Framework 2.0 encoding used to import the XML file. For example,
/e:utf-7 will use Unicode (UTF-7) encoding. Encoding is automatically detected whenever possible. If
the encoding cannot be detected, UTF-8 is used.
/v Validates the XML definitions for the work item type, link type, or global workflow without importing
them.
You can export the agile process template to disk, then import the work items into your existing project. You may need the TFS Power Tools to do this.
I may be too late for this question, but the TFS Integration Platform tools could really help here.
See this question on server fault that details on how to move from Scrum For Team System V2 to Microsoft Visual Studio Scrum 1.0.
You would need to setup your own mappings to move from your templates to the target template, but the process is the same.
Please note witadmin.exe could help in some scenarios but TFS Integration Platform is your ultimate choice to achieve this task. There is a user voice item still pending. Please check this SO thread.
I think the best way to accomplish this is to create a new Team Project with "the new" process template and use the TFS Integration tool to migrate your existing WorkItems and choose create a new branch from Source Control, so you'll have new work Items (with the new workflow) and the source control history (as well). You'd even do this across versions of TFS!! (On the case interested on migrate TFS 2005/2008/2010)
Another way might be to use the WorkItem Templates, but I think this is more a kind-of visual style (I've not much experience) applied to the Work Item. To do so, just right click on your project, import the WITDefinition and apply the template by selecting Apply template on desired WorkITems.