One of my favourite timesaving commands is gam <user> transfer ownership, moving a folder and all its contained files to a new owner.
However most of the time it is important to specify a new parent destination, as the process of transferring ownership of a folder and its files but leaving it in place in the Drive of the original owner can cause confusion if the new owner never had access to it before. They end up owning the folder but it doesn't show up in their Drive unless they search for it and then give it a home.
Hence I can use <DriveFileParentAttribute> to explicitly give the transferred folder a new home.
But that only allows me to place the folder in a known subfolder that I've already identified. What I would like to do is tell GAM to place the transferred folder in the root of the new owner's Drive. As far as I can tell the top level of your personal Drive doesn't have a distinct ID, unlike say the root of a Shared Drive which always exposes the folder ID in its url.
The url path of your Drive root is "my-drive" but GAM cannot parse that when doing the transfer ownership command and so searches for and fails to locate an actual folder with that name.
Is there a way around this?
-- James Masterton
Cloud Collaboration Analyst
Group Service Delivery - Group IT - Rentokil Initial