You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The technicians have requested functionality to automatically select points that are duplicate (same value and same timestamp) and overlapping (same timestamp but different values).
The first case can occur when a user has added points using the Add Point function, but some of those points already existed in the series. It is impossible to visually identify this since the points overlap. When the user tries to save the data series, it results in an error. They can then track down the overlapping point noted in the error message, but there may be more than one of these points, so they then have to go through the process multiple times.
The second case may occur for various reasons. This is not prevented by the business rules of the database, so it is desirable to have a method for identifying overlapping points in case this is not intentional or doesn't make sense for the data series.
I think that this should be added as an option on the Filter Points form. We can discuss more if needed.
The text was updated successfully, but these errors were encountered:
We need to get this issue addressed and a release out with all of our current functionality included ASAP. @sreeder I know you are working on the release problem. Can we make a goal to get that resolved this week?
The technicians have requested functionality to automatically select points that are duplicate (same value and same timestamp) and overlapping (same timestamp but different values).
The first case can occur when a user has added points using the Add Point function, but some of those points already existed in the series. It is impossible to visually identify this since the points overlap. When the user tries to save the data series, it results in an error. They can then track down the overlapping point noted in the error message, but there may be more than one of these points, so they then have to go through the process multiple times.
The second case may occur for various reasons. This is not prevented by the business rules of the database, so it is desirable to have a method for identifying overlapping points in case this is not intentional or doesn't make sense for the data series.
I think that this should be added as an option on the Filter Points form. We can discuss more if needed.
The text was updated successfully, but these errors were encountered: