I have come across an odd situation in MOSS 2007. I create a list. Put some items in the list and create a SharePoint designer workflow that is associated with the list. Later I save the list definition without content. I then create a new list from the template and add items. The workflow fires and pulls data from the orginal list. What is going on here? If I delete the original list, SharePoint still pulls in data from the original list. Has anyone seen this before? Do you know of any sources that describe the problem?

SharePoint Designer Workflows are associated with one list only. In fact, if you take a look to the Workflow source files, all references to the list uses the GUID. So, I'm afraid you'll have to create a new Workflow for the new list instance. Cheers.Miguel Ballesteros

Hi, I agree with Miguel Ballesteros.If you want to move the workflow to another list, an alternative is to convert the SPD workflow into a Visual Studio workflow which can be more easily deployed to many different places. Reference below will walk you through.http://blogs.msdn.com/sharepointdesigner/archive/2007/07/06/porting-sharepoint-designer-workflows-to-visual-studio.aspx Hope it helps.Lily Wu

It's a SharePoint bug - when you create a STP the workflow associations should be deleted from the STP but are not and then you get a mess - your new list launches a workflow that is workfing on another list.Pawe Wrbel Datapolis.com

It's a SharePoint bug - when you create a STP the workflow associations should be deleted from the STP but are not and then you get a mess - your new list launches a workflow that is workfing on another list.Pawe Wrbel Datapolis.com