Kelly Linton-Selkirk

My feedback

  1. 58 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Kelly Linton-Selkirk supported this idea  · 
  2. 410 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  Jon Hardy responded

    Without going into the technical detail; the previous value made available in conditional start is actually the current value just before any updates are made to the item. When the item is updated, we lose the ability to get the value prior to the update.

    To restate the workaround as indicated in the idea; create an additional column in the list or library and update this with the current value of the column of interest. Then when the actual column is updated, the previous value is still available in the additional column. Of course one need not make this additional column visible in the view or Form so the users are not confused.

    Kelly Linton-Selkirk supported this idea  · 
    An error occurred while saving the comment
    Kelly Linton-Selkirk commented  · 

    This would solve so many synchronization issues. I have 5 services , each service has a main project window that creates the standard tasks for the services in a team task list. When tasks are completed I update the main project list for that service in order to track project completion. I use 2 fields from the team task list to identify the correct record in the project list. But if those 2 fields are changed I need to sync the change to the Project list but I cant do that without knowing the previous value to ensure I am updating the correct record.

Feedback and Knowledge Base