<?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 Re: After upgrade to 20.2.2.2. I can no longer change cloud config groups in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/after-upgrade-to-20-2-2-2-i-can-no-longer-change-cloud-config/m-p/78012#M7666</link>
    <description>&lt;P&gt;Thanks, Sam. I took a little time to check the basic browser add-in conflict route, but no change. I'll refer it to support.&lt;/P&gt;</description>
    <pubDate>Tue, 31 Mar 2020 00:55:56 GMT</pubDate>
    <dc:creator>andrew_vernon</dc:creator>
    <dc:date>2020-03-31T00:55:56Z</dc:date>
    <item>
      <title>After upgrade to 20.2.2.2. I can no longer change cloud config groups</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/after-upgrade-to-20-2-2-2-i-can-no-longer-change-cloud-config/m-p/78010#M7664</link>
      <description>&lt;P&gt;I'm getting the error "&lt;B&gt;The item cannot be saved because the name null already exists." &lt;/B&gt;This didn't happen previously, and only occurs when making changes to an existing group. Creating a new group and adding devices to it works as expected. Was there a change to cloud config group functionality that may cause this?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 02:40:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/after-upgrade-to-20-2-2-2-i-can-no-longer-change-cloud-config/m-p/78010#M7664</guid>
      <dc:creator>andrew_vernon</dc:creator>
      <dc:date>2020-03-27T02:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrade to 20.2.2.2. I can no longer change cloud config groups</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/after-upgrade-to-20-2-2-2-i-can-no-longer-change-cloud-config/m-p/78011#M7665</link>
      <description>&lt;P&gt;There shouldn't be any changes that would cause that error, I would recommend opening a technical support case so our engineers can work on this with you. &lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 20:55:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/after-upgrade-to-20-2-2-2-i-can-no-longer-change-cloud-config/m-p/78011#M7665</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2020-03-27T20:55:42Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrade to 20.2.2.2. I can no longer change cloud config groups</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/after-upgrade-to-20-2-2-2-i-can-no-longer-change-cloud-config/m-p/78012#M7666</link>
      <description>&lt;P&gt;Thanks, Sam. I took a little time to check the basic browser add-in conflict route, but no change. I'll refer it to support.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2020 00:55:56 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/after-upgrade-to-20-2-2-2-i-can-no-longer-change-cloud-config/m-p/78012#M7666</guid>
      <dc:creator>andrew_vernon</dc:creator>
      <dc:date>2020-03-31T00:55:56Z</dc:date>
    </item>
  </channel>
</rss>

