narges mohamadi

My feedback

  1. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  9 - Nintex Hawkeye » Data Sources  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    narges mohamadi commented  · 

    I am wondering if there are any updates on the status of this feature? Are there any timeframes around when this can be released?

    An error occurred while saving the comment
    narges mohamadi commented  · 

    I am wondering if there are any updates on the status of this feature? Is there any timeframe around when this feature can be released?

  2. 138 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  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    narges mohamadi supported this idea  · 
  3. 97 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    At this stage we have no plans to change the validation message location for Classic Forms. We recommend you look at Responsive Forms if you users prefer the validaiton message below the field.

    Once we have shipped Universal Forms for SharePoint, we will revisit the Classic experience.

    Cheers,
    Euan

    An error occurred while saving the comment
    narges mohamadi commented  · 

    I hope Nintex can address this issue. It has been asked by our end users many times that they want to see error messages under each field as the OOTB SharePoint form does, instead of a Summary of all errors

    narges mohamadi supported this idea  · 
  4. 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.

    narges mohamadi supported this idea  · 

Feedback and Knowledge Base