<?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: Chrome device custom attributes in Peer-Peer Topics</title>
    <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/144852#M4055</link>
    <description>&lt;P&gt;Exactly. There are four (4) open fields, which do&amp;nbsp;&lt;EM&gt;not&lt;/EM&gt; have to be used for what they are called. They can be used for anything at all. They are just text fields.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Location&lt;/EM&gt;, &lt;EM&gt;Asset ID&lt;/EM&gt;, &lt;EM&gt;User&lt;/EM&gt;, &lt;EM&gt;Notes&lt;/EM&gt;. They are not used for anything specific, and can contain any type of data, and also a lot of data. I don't know the upper limit, but it's quite a lot. Perhaps &lt;EM&gt;Notes&lt;/EM&gt; has the highest limit, but I haven't tested.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Apr 2025 05:31:12 GMT</pubDate>
    <dc:creator>Kim_Nilsson</dc:creator>
    <dc:date>2025-04-17T05:31:12Z</dc:date>
    <item>
      <title>Chrome device custom attributes</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/143097#M4039</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm surprised to find that custom &lt;FONT color="#FF6600"&gt;&lt;STRONG&gt;device&lt;/STRONG&gt;&lt;/FONT&gt; attributes, similar to the custom &lt;FONT color="#FF6600"&gt;&lt;STRONG&gt;user&lt;/STRONG&gt;&lt;/FONT&gt; attributes available in Google Workspace, are not supported for &lt;STRONG&gt;&lt;FONT color="#FF6600"&gt;Chrome devices&lt;/FONT&gt;&lt;/STRONG&gt;. We require fields such as purchase order number, warranty information, device color, Is 1-to-1 and specialized specifications for effective device management.&lt;/P&gt;&lt;P&gt;Am I overlooking something? Why isn't there more widespread demand for custom device attributes?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 18:49:09 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/143097#M4039</guid>
      <dc:creator>sampapa</dc:creator>
      <dc:date>2025-04-10T18:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: Chrome device custom attributes</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/143136#M4040</link>
      <description>&lt;P&gt;I've never thought to look, but this is an awesome idea!&lt;/P&gt;&lt;P&gt;I also do not see this feature...&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 18:54:09 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/143136#M4040</guid>
      <dc:creator>kaned</dc:creator>
      <dc:date>2025-04-10T18:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: Chrome device custom attributes</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/143139#M4041</link>
      <description>&lt;P&gt;Not perfect, but you could use the description field for that. Ie: "PO=####,WarrantyExpiry=dd/mm/yyyy,color=pink,1to1=true".&lt;/P&gt;&lt;P&gt;You can then search those fields from Workspace. Or use a tool like GAT+ or GAM to search that field.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 20:48:59 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/143139#M4041</guid>
      <dc:creator>Olger</dc:creator>
      <dc:date>2025-04-10T20:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: Chrome device custom attributes</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/144852#M4055</link>
      <description>&lt;P&gt;Exactly. There are four (4) open fields, which do&amp;nbsp;&lt;EM&gt;not&lt;/EM&gt; have to be used for what they are called. They can be used for anything at all. They are just text fields.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Location&lt;/EM&gt;, &lt;EM&gt;Asset ID&lt;/EM&gt;, &lt;EM&gt;User&lt;/EM&gt;, &lt;EM&gt;Notes&lt;/EM&gt;. They are not used for anything specific, and can contain any type of data, and also a lot of data. I don't know the upper limit, but it's quite a lot. Perhaps &lt;EM&gt;Notes&lt;/EM&gt; has the highest limit, but I haven't tested.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Apr 2025 05:31:12 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/144852#M4055</guid>
      <dc:creator>Kim_Nilsson</dc:creator>
      <dc:date>2025-04-17T05:31:12Z</dc:date>
    </item>
    <item>
      <title>Re: Chrome device custom attributes</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/144853#M4056</link>
      <description>&lt;P&gt;With my free and open-source script for Google Sheets, you can easily manipulate those fields for many devices without paying for GAT+ or diving in the deep end with GAM7 (&lt;EM&gt;&lt;STRONG&gt;all&lt;/STRONG&gt;&lt;/EM&gt; Workspace admins should still at least learn how to swim&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":beaming_face_with_smiling_eyes:"&gt;😁&lt;/span&gt;).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CB_Inventory&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/NoSubstitute/CB_Inventory/" target="_blank"&gt;https://github.com/NoSubstitute/CB_Inventory/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Apr 2025 05:34:04 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/144853#M4056</guid>
      <dc:creator>Kim_Nilsson</dc:creator>
      <dc:date>2025-04-17T05:34:04Z</dc:date>
    </item>
    <item>
      <title>Re: Chrome device custom attributes</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/144938#M4058</link>
      <description>&lt;P&gt;&lt;FONT size="4" color="#000000"&gt;Hi, we already use the existing&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;Location&lt;/EM&gt;&lt;/STRONG&gt;&lt;SPAN&gt;,&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;Asset ID&lt;/EM&gt;&lt;/STRONG&gt;&lt;SPAN&gt;,&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;User&lt;/EM&gt;&lt;/STRONG&gt;&lt;SPAN&gt;,&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;Notes &lt;/EM&gt;&lt;/STRONG&gt;fields.&amp;nbsp; I've considered using the notes field with an element style syntax such as:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;po&amp;gt;555333555&amp;lt;/po&amp;gt;
&amp;lt;color&amp;gt;red&amp;lt;/color&amp;gt;
&amp;lt;warranty&amp;gt;5&amp;lt;/warranty&amp;gt;
&amp;lt;type&amp;gt;staff&amp;lt;/type&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="tahoma,arial,helvetica,sans-serif" size="4" color="#000000"&gt;I still would like Google to support custom fields.&amp;nbsp; It would just make their product better and is common functionality found in other MDM or management solutions.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="tahoma,arial,helvetica,sans-serif" size="4" color="#000000"&gt;This data is fed into our main IT ticketing and inventory system.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2025 16:15:44 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Chrome-device-custom-attributes/m-p/144938#M4058</guid>
      <dc:creator>sampapa</dc:creator>
      <dc:date>2025-04-18T16:15:44Z</dc:date>
    </item>
  </channel>
</rss>

