Chad Mulready

My feedback

  1. 125 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chad Mulready supported this idea  · 
  2. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Chad Mulready commented  · 

    Additional information: So we have the requirement for "Stages" in an employee review form. Once a stage is closed, the previous stage fields become read only, and as there are only 2 rows to view.... it just makes the user experience ....restricted.... when they have to scroll through 2 rows to view the previous stage.

    Chad Mulready shared 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…)
    0 comments  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Chad Mulready shared this idea  · 
  4. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chad Mulready shared this idea  · 
  5. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Chad Mulready commented  · 

    Hi,
    Not sure if this is what you were looking for, but have you tried the following workaround:

    Create a field or variable with an a value using the following Inline function "NewGuid" ?

    Then use this field as a named control in the calculate field?

    Regards

    Chad

  6. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chad Mulready shared this idea  · 

Feedback and Knowledge Base