taers232c / GAMADV-XTD3

Command line tool to manage Google Workspace
691 stars 86 forks source link

gender.addressMeAs is not usable as a field in tag replacement #327

Closed chromestrong closed 1 month ago

chromestrong commented 1 year ago

gam_error Howdy Team,

We are currently trying to set up signatures for our account objects and we noticed that GAMADVXTD3 does not recognize "gender.addressMeAs" as a field when doing tag replacement.

This appears to be bug since it also doesn't show up as a field when doing "gam info user", but does when you do "gam print users basic" or "gam print users full" commands.

Please assist.

Thanks Team

taers232c commented 1 year ago

Implemented 6.32.02

gam info user shows gender fields for me, test and report

chromestrong commented 1 year ago

There does appear to be a delay since the information is still not presented in Gam Info User, only gender.type is shown. However, it does now appear that gender.AddressMeAs works with tag replacement.

taers232c commented 1 year ago

Send me a Meet/Zoom invitation, info user works for me, let's figure out why it doesn't work for you.

Rpss

taers232c commented 1 year ago
$ gam info user testsimple fields gender noaliases nogroups
User: testsimple@rdschool.org
  Settings:
  Gender:
    type: other
      customGender: Tech
    addressMeAs: Yo
$ gam update user testsimple gender male addressmeas Dude
User: testsimple@rdschool.org, Updated
$ gam info user testsimple fields gender noaliases nogroups
User: testsimple@rdschool.org
  Settings:
  Gender:
    type: male
    addressMeAs: Dude
$ gam update user testsimple gender YoYo addressmeas Yo
User: testsimple@rdschool.org, Updated
$ gam info user testsimple fields gender noaliases nogroups
User: testsimple@rdschool.org
  Settings:
  Gender:
    type: other
      customGender: YoYo
    addressMeAs: Yo
chromestrong commented 1 year ago

Yep, it looks like it could be a propagation delay if the employee updates their pronouns using the UI. I am seeing the values correctly for gender.type and gender.addressMeAs for an account object that set them yesterday. I am only seeing the values correctly for gender.type for an account object that set them earlier today. I will give it 24 hours and follow up. Thank you for the fast response and support!

chromestrong commented 1 year ago

Can you confirm that gender.AddressMeAs maps to the values set by the users at this link: https://myaccount.google.com/personal-info?

It doesn't appear to be.

chromestrong commented 1 year ago

Right now it looks like that 'gender.type' maps to the fields at this link: https://myaccount.google.com/gender But 'gender.AddressMeAs' doesn't map to the fields at this link: https://myaccount.google.com/profile/pronouns

taers232c commented 1 year ago

Eric,

I don't have a license that lets me set pronouns, send me a Meet/Zoom invitation.

Ross

On Mon, Feb 13, 2023 at 7:53 AM Eric @.***> wrote:

Right now it looks like that 'gender.type' maps to the fields at this link: https://myaccount.google.com/gender But 'gender.AddressMeAs' doesn't map to the fields at this link: https://myaccount.google.com/profile/pronouns

— Reply to this email directly, view it on GitHub https://github.com/taers232c/GAMADV-XTD3/issues/327#issuecomment-1428182278, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL7JQGIF2VBI2AF63FDWXJKIPANCNFSM6AAAAAAUX6NN3E . You are receiving this because you commented.Message ID: @.***>

-- Ross Scroggs @.***

chromestrong commented 1 year ago

I have a ticket open with Google Support. I can see in the API Explorer that values set in the GUI don't show up in the API field but show up in the Contacts Directory, and values set in the API field show up in the API BUT don't show up in the Contacts Directory.