Stump the Panel » SharePoint Workflow for All Users

Workflow to update 'child' items when a 'parent' item is changed

(2 posts)
  • Started 2 months ago by NancyCentury
  • Latest reply from bhorner
  1. NancyCentury
    Member

    My Vendor List ("parent") contains information about each company- address, vendor type, ID number, etc. On this list, each vendor is a unique item that only appears once, and its ID number only appears once.

    My Vendor Contact List ("child") contains information about the people who work at these companies. Each list item contains the matching vendor ID number of the company for whom they work.

    When a new list item is created, only the ID number and the person's name are needed- all the other fields populate via workflow off the "parent" list using the vendor ID as a point of commonality. Each person's name is unique to this list, but a company (therefore a vendor number) may appear more than once.

    I am stuck trying to ensure that all "child" items on the Contact list which share the "parent's" vendor number will update accordingly should the "parent" item change (for the fields they share). I created a workflow that worked, but only for one ID number per vendor on the child list.

    For example, Vendor A has 3 managers listed on the Contact list. If Vendor A is changed from "active" to "inactive", my workflow only pushed that change out to the first manager listed on the Contact list.

    Is this doable using only SPD capability (it's all I have). Thanks!

    Posted 2 months ago #
  2. You can accomplish this, but it takes some funny business with SPD. Essentially, you will need to create a Looping Workflow. There are several tutorials around the web but you will essentially do the current action you have been doing but updating an item in another list (preferably create a Loop Controller list that, when any item is updated, kick off the workflow). I used this to help update information across a large list and here's kinda how it looked:

    Loop Controller List - has 2 fields called "Last ID Number Processed" and "Title"
    Workflow on this list is set automatically on updates and will set a "Processed" column in my second list to "No".

    Second List - has multiple fields but ends with a "Processed" column.
    Workflow on this list updates itself automatically on change and will re-update all information based on an ID# and then sets the "Processed" column to "Yes" and then sets the "Last ID Number Processed" to the Current Item's ID...which, in turn, kicks off the workflow again in a looping process until it finishes.

    You'll need something like this but modified to only hit the ones where the ID is the same as the Parent List's ID. Hope that helps get you started.

    Posted 2 months ago #

RSS feed for this topic

Reply

You must log in to post.