-
Notifications
You must be signed in to change notification settings - Fork 63
How to enable the Asset ID field when I have enabled this toggle in settings? #47
Comments
Hi, confirmed, I tried this some time ago and had the same result. |
I've been having to manually update datastore, on behalf of our desktop team who don't have gcp access, to get the asset tags to work with auditing a shelf |
How did you do that?
…On Mon, Apr 29, 2019, 7:25 PM Gareth Mcshane ***@***.***> wrote:
I've been having to manually update datastore, on behalf of our desktop
team who don't have gcp access, to get the asset tags to work with auditing
a shelf
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#47 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKLPRKFVESOGWUQ6I4GNKNDPS6GWRANCNFSM4HHECXEQ>
.
|
Hi "iamgeef" thank you for your comment but... I tried editing the asset_tag directly on the entity in the GCP, but in some part of the process the relation is lost and the device is not recognized, so at the end the "device" become a "ghost" and it cannot be unrolled, audit, extend the loaner period, etc. I tried with "Clear device (in settings)" but this did not work. In recap, I don not recommend to do this manually in the GCP. Does anybody has another suggestion? Thank you in advance for your time. Kind regards, |
Just a bit of clarification here on using asset tag.
|
Raises an interesting question of what the "Use asset tags" option does if the feature isn't available without creating it ourselves... I've got a workaround, that works for my use case anyway. Maybe it'll help others. We use the 'Asset ID' field of the chrome_devices GSuite config to store our asset tags, entered during Enterprise Enrollment process by our desktop team, BUT the Directory API doesn't provide the ability to get the asset tag field: https://developers.google.com/admin-sdk/directory/v1/reference/chromeosdevices It does allow you to get the contents of the 'notes' field so I've been able to convince the desktop team to also enter the asset tag into the devices 'notes' field at enrollment time. It's then just 4 lines that need to be changed - sorry for the formatting...: loaner/web_app/constants.py - appending 'notes' as a new field mask: loaner/web_app/backend/clients/directory.py - adding ASSET_TAG = u'notes'
loaner/web_app/backend/models/device_model.py - adding a new line to assign the notes to device.asset_tag field: I still have to enroll with the serial number, but it now gets the asset Id. |
If anyone else uses the same 'Asset ID' field, I've raised a feature request to get the 'Asset ID' field available in the Directory API to avoid using the 'notes' field to store the ID: |
using annotatedAssetId instead of notes in the code above worked for me. |
Expected Behaviour
In settings I have enabled the toggle "Use asset tags", in order to use the asset id instead of the serial number of the device
Actual Behaviour
It's not asking for he asset id when a new device is enrolled, also I cannot use the asset id in order to audit a shelf.
Steps to Reproduce
Enable the toggle option and add a new device or audit a shelf
Thank you very much in advance for your help.
The text was updated successfully, but these errors were encountered: