Reed Carr

My feedback

  1. 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.

    An error occurred while saving the comment
    Reed Carr commented  · 

    Jon Hardy - This isn't making any sense. If the value is gone once the item is updates, and workflows that run when items are updated can detect the "previous value" even if the value changed during edit, then why are the values not available during workflow actions in addition to workflow initiation? Put another way. If the workflow initiation condition can evaluate after the value has changed, why can't conditions evaluate based on the same value(s) after workflow initiation? Many of the business processes I work on need this for not just 1 or two field, but dozens. It would be a huge value add to be able to access that data. Please add it to the path!

    Reed Carr supported this idea  · 
  2. 23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Reed Carr supported this idea  · 
  3. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Reed Carr shared this idea  · 
  4. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  1 - Nintex Workflow for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Reed Carr commented  · 

    One note, we got around this by having our users with design permissions go to Site Settings and use the Scheduled Workflows link in the Nintex Workflow section.

  5. 43 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  ·  Euan Gamble responded

    Good suggestion Nicole. I will add this suggestion to the backlog as we are starting the List Lookup control for Universal Forms.

    Cheers,
    Euan

    Reed Carr supported this idea  · 
  6. 252 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Reed Carr supported this idea  · 

Feedback and Knowledge Base