Chad Mulready

My feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Chad Mulready supported this idea  · 
  2. 22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers,
    Euan

    An error occurred while saving the comment
    Chad Mulready commented  · 

    Please see attached for sample screenshots

    An error occurred while saving the comment
    Chad Mulready commented  · 

    Hi Palesa,

    We too have the need to prevent users from deleting rows in a repeating section, essentially as you say, to preserve data. We don't want users creating a row of data, then come back 6months later and delete the row, we need the data to persist.

    In Modern? we were able to hide the delete button using a richtext field and editing the html code to add styling to remove the button as follows:

    <style>.nf-repeater-deleterow-image { display: none;} </style>

    However in the "New Responsive" design this workaround doesn't seem to be there, or its changed name.

    Either way, it may be a deal breaker to go to the new responsive form if we "lose" the ability to prevent users from removing repeating rows.

    Ideally, it would be great if there was a checkbox that you could mark to "Prevent Row Deletion" that could hide the button..

    Regards
    Chad

    Chad Mulready supported this idea  · 
  3. 125 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.

    Cheers,
    Euan

    Chad Mulready supported this idea  · 
  4. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers,
    Euan

    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  · 
  5. 7 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Chad Mulready shared this idea  · 
  6. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Chad Mulready shared this idea  · 
  7. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers,
    Euan

    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

  8. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers, Euan

    Chad Mulready shared this idea  · 

Feedback and Knowledge Base