<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic GlobalDashboard search issues in HPE OneView</title>
    <link>https://community.hpe.com/t5/hpe-oneview/globaldashboard-search-issues/m-p/6996486#M2579</link>
    <description>&lt;P&gt;Hello everybody!&lt;/P&gt;&lt;P&gt;I like the idea of ​​the OV and GD product and really appreciate your work, but there are flaws that nullify the entire user experience. I mean the "convenience" of searching and sorting data in the Dashboard applince OneView applince.&lt;BR /&gt;Example:&lt;BR /&gt;I need to add only the DL 380 Gen8 servers to the new "Group". I think, this way i can see in "Server Firmware Details" report data relevance only to DL380 Gen8 hardware. Ok, I'm writing in the search line " model: "Prolian DL380 Gen8" ". As a result, I get list of 650 different DL380, but all possible generations. Ok, I think I'll sort it out, and I'll select DL Gen 8 all at once. They will be a contract, and a group selection will solve the problem.&lt;BR /&gt;No, there is no sorting, just like group selection too.&lt;/P&gt;&lt;P&gt;This is cruel in relation to the user. I understand that all this can be done in the POSH-HPOneView. But why then was to do a search string, if it does not work at all?&lt;/P&gt;&lt;P&gt;Version 1.40.01-0329917 Released 2018-01-23&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Feb 2018 13:09:18 GMT</pubDate>
    <dc:creator>Vito_B</dc:creator>
    <dc:date>2018-02-09T13:09:18Z</dc:date>
    <item>
      <title>GlobalDashboard search issues</title>
      <link>https://community.hpe.com/t5/hpe-oneview/globaldashboard-search-issues/m-p/6996486#M2579</link>
      <description>&lt;P&gt;Hello everybody!&lt;/P&gt;&lt;P&gt;I like the idea of ​​the OV and GD product and really appreciate your work, but there are flaws that nullify the entire user experience. I mean the "convenience" of searching and sorting data in the Dashboard applince OneView applince.&lt;BR /&gt;Example:&lt;BR /&gt;I need to add only the DL 380 Gen8 servers to the new "Group". I think, this way i can see in "Server Firmware Details" report data relevance only to DL380 Gen8 hardware. Ok, I'm writing in the search line " model: "Prolian DL380 Gen8" ". As a result, I get list of 650 different DL380, but all possible generations. Ok, I think I'll sort it out, and I'll select DL Gen 8 all at once. They will be a contract, and a group selection will solve the problem.&lt;BR /&gt;No, there is no sorting, just like group selection too.&lt;/P&gt;&lt;P&gt;This is cruel in relation to the user. I understand that all this can be done in the POSH-HPOneView. But why then was to do a search string, if it does not work at all?&lt;/P&gt;&lt;P&gt;Version 1.40.01-0329917 Released 2018-01-23&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2018 13:09:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-oneview/globaldashboard-search-issues/m-p/6996486#M2579</guid>
      <dc:creator>Vito_B</dc:creator>
      <dc:date>2018-02-09T13:09:18Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalDashboard search issues</title>
      <link>https://community.hpe.com/t5/hpe-oneview/globaldashboard-search-issues/m-p/6998145#M2580</link>
      <description>&lt;P&gt;search for "Proliant DL380 Gen8".&amp;nbsp; remove the model&amp;nbsp;prefix, and it will find what you are expecting.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2018 22:33:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-oneview/globaldashboard-search-issues/m-p/6998145#M2580</guid>
      <dc:creator>bsoutham</dc:creator>
      <dc:date>2018-02-26T22:33:20Z</dc:date>
    </item>
  </channel>
</rss>

