Kenneth Barber

My feedback

  1. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  2. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  3. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  4. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  5. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  PI Server » PI Builder  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber commented  · 

    Hi Chris. Is there a timeline for the fix?

    Kenneth Barber commented  · 

    Actually, that doesn't achieve what I want. I still get a border of blank, modified cells.

    I understand that the blank border helps to isolate PI Builder data into its own "current region" (that's an Excel term), but I don't understand why the border cells need to be modified by PI Builder, especially when I import data into a new sheet.

    Kenneth Barber commented  · 
    Kenneth Barber shared this idea  · 
  6. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  7. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Server » Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber commented  · 

    Replace "PI OLEDB Enterprise" with "PI SQL Client OLEDB".

    Kenneth Barber commented  · 

    I forgot to use the almighty buzzword. If users can query the PI Data Archive more easily, then that makes the PI Data Archive more EXTENSIBLE.

    Kenneth Barber shared this idea  · 
  8. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  9. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  PI Server » PI Builder  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber commented  · 

    James, if by "break", you mean "change", then yes, my suggestion will break the existing behaviour. And so will every other change suggested on OSIsoft UserVoice.

    Documenting a program's behaviour is not the end of the road. Improving the behaviour is the next step. I've already described what is wrong with the current behaviour and how to fix it. I'm not sure why you feel that this change isn't worthwhile.

    Is there something obviously wrong with a choice menu popping up? Am I missing something?

    Kenneth Barber commented  · 

    Stephen, what if, when the user tries to publish both excdev and excdevpercent or both compdev and compdevpercent, they are given the choice to either stop the publish or choose one of excdev or excdevpercent and/or one of compdev and compdevpercent to be edited? Then that use case that you mentioned would not be broken, and the user will not be forced to delete columns.

    Kenneth Barber commented  · 

    Stephen, I was thinking more along the lines of throwing the error if both excdev and excdevpercent or both compdev and compdevpercent are present when publishing, regardless of whether either of them was changed.

    PI Builder assumes that anything that is published is an edit, regardless if the value actually changed or not. That is the assumption that I'm rolling with.

    Kenneth Barber shared this idea  · 
  10. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  11. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  12. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  13. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  14. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  15. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  16. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » Asset Framework (AF)  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  17. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  18. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  19. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber shared this idea  · 
  20. 1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    Kenneth Barber supported this idea  · 
    Kenneth Barber commented  · 

    These tables have bad sizing behaviour:
    Operations → Message Logs → PI Message Log (last 2 columns)
    Operations → Message Logs → Local PI Message Log (last 2 columns)
    Operations → Snapshot And Archive Statistics (last column)

    At the time that I posted my suggestion, I'm pretty sure that there were more. Maybe they've all already been fixed.

    Wouldn't it be more efficient to reuse the same resizing code across all plugins?

    Kenneth Barber shared this idea  · 

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED