Hello, I'm trying to create 2 lists on the same SharePoint site: One to track small issues, another that can be used to track small issues that have been escalated to larger ones. For this example, let's call them "Small Issues (Source)" and "Large Issues (Target)". The only difference between the 2 lists is that the "Large Issues" list has a few extra columns (extra detail, names, etc). The rest of the fields are identical. So, Small has 5 columns while Large may have 8 (5 from Small and 3 of its own). If an item is promoted from the Small list to the Large list, I would like it the common fields to be synchronized, so it can be edited from either side and the data copies over. Not all items in the Small list will make it to the Large list, however all items in the Large will have an equivalent in the Small list. Any ideas on how to make this work? I'm open to any solutions, however here is the path I've been taking so far: So far, by using a workflow I created, a small issue can be escalated by manually launching the workflow (using the "Workflows" button), which then copies the issue to the Large Issues list including all the fields that are common. I'm also copying the GUID from the original to the new list, so that we can find the item in the original list. I then have 2 workflows (on attached to each list) that when an item is modified, it automatically triggers to copy the data over to the other list. The catch is, an infinite loop begins... How can I fix this?

Your path is exactly right. I think you have created Visual Studio worklow, where is infinite loop ?w: http://www.worldofsharepoint.com | t: @sharesandip

Why not use just the one list, and create two content types? CT1 (small issue) would have the relevant metadata, and CT2 (large issue) would have the larger amount of metadata. Then, you can change the content type within the UI when the issue escalates, it'll expose the other columns, and you can add the information as necessary. Then you can control what's seen via the list views, filtering by the relevant content type (or whatever you'd like). This way, no copying of items across to different lists, and worrying about that sync process. Thoughts? - M- Michael Mukalian - 2010 MS MVP SharePoint Services - MCTS: MOSS 2007 Configuration - http://www.mukalian.com/blog

That is a fantastic solution, I hadn't thought of that. Thank you very much. Now, how can I control who is allowed to switch content types? I only want a few users to be able to escalate an issue (in other words, switch content types). I want anyone to be able to create new items (CT1), but only a few people to be able to create/switch to CT2.

That is a fantastic solution, I hadn't thought of that. Thank you very much.