Skip to content

Water Distribution

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

2 results found

  1. roll back commit history

    We can see what the commit history is, but if you made a mistake and committed it there's no way to go back without making a new branch.

    Would be good to be able to roll back changes to a selected point in the commit history so your mistake isn't locked in for eternity.

    Would also facilitate trialing solutions without cluttering up commit history with garbage.

    4 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

    1 comment  ·  Operational Modeling  ·  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)
  2. Push Changes From Parent to Child(ren) Scenarios

    Allow changes made in a parent scenario to push through and update all child scenarios unless that link is broken in the child scenario(s).

    This goes along with the improvement suggestion titled "Data Sets" by Kathryn Carreira. The Scenario and Data Sets organization needs to be improved in InfoWater Pro as other software already excels in this area. Right now if something changes in one scenario it has to be manually updated in all child scenarios, this becomes exponentially time consuming with larges model and multiple scenarios.

    7 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  ·  Operational Modeling  ·  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)

    To be clear, changes to the parent can cascade to all child scenarios as long as the same data set is used.

    To inheret changes where datasets are different would introduce complexity and room for error in model management.


    This seems to be specifically a request for a new parent-child relationship among data sets which could exist parallel and independent of the scenario relationships. This way a child scenario could use a child dataset that varies at certain nodes, but still inherets changes from the parent as long as they're still matching - the same way that InfoWorks software handles scenarios. I see large benefits of this approach but it could certain confuse many modelers.


    This is valuable feedback as we discuss model data management in the cloud. Thank you.

  • Don't see your idea?

Feedback and Knowledge Base