Child Item

The remote server returned an error: (422) Unprocessable Entity.

I'm trying to list all the file and folders in a Dropbox Teamspace and getting the following error

"{"error":{".tag":"invalid_root","invalid_root":{".tag":"team","home_namespace_id":"retracted","home_path":"/retracted Dropbox Team Spaces","root_namespace_id":"retracted"}},"error_summary":"invalid_root/"}"

This all looked to be working as expected until a few weeks ago.

If anyone could help it would be much appreciated

Find more posts tagged with

Developers

Accepted answers

iNeil

Hello @awb ,

Based on the error message "invalid_root", this is occurring as the Dropbox-API-Path-Root header "root_namespace_id" value is incorrect. Please cross check if you are using the correct "root_namespace_id" by executing the 2/users/get_current_account endpoint. You can also test the endpoint using our Dropbox API explorer.

Please bear in mind that there is a possibility that your account has been updated to our new team space functionality. For further information on the latest updated team space, please review the following link:

API updates to better support team spaces

While implementing the Dropbox API with the updated team space, you will need to configure your API calls to operate within the "team space", in order to interact with files/folders in the team space. To do so, you'll need to set the "Dropbox-API-Path-Root" header with your Dropbox API request. For further information, please review the following link:

All comments

iNeil

API updates to better support team spaces

awb

Hi,

Appologies in the delay in getting back to you.

"Please bear in mind that there is a possibility that your account has been updated to our new team space functionality. For further information on the latest updated team space, please review the following link:"

This was orinally created as a Team Space, so assumed nothing has changed.

Have all Dropbox customer been migrated to Team Spaces now?

Thanks

Greg-DB

Teams are being updated to the updated team space, though not all teams have been yet.

awb

Thanks Greg, is the plan to move all of your customers on to this? Or is this still optional?

Greg-DB

Dropbox is planning to migrate all teams to the updated team space configuration.

awb

@Greg-DB Just wanted quickly followup on something. When you migrate teams to the new team space configuration.

Do the team folder ids change at all? Just noticed some odd behaviour in something I am working on.

Thanks

Greg-DB

The team folder IDs of existing team folders themselves shouldn't change, though member roots can change. There are different scenarios and variables though, e.g., a team migrating from no team space to the updated team space, versus migrating from the team space to the update team space, so please feel free to share the details of any specific issue so we can advise accordingly.

awb

Thanks for the response @Greg-DB if I were to list folders in a namespace as an admin and

then as a user. would the folder id be different.

I guess I can test this out when I get a chance.

awb

So I've tested the above.

Ran list folders as member, using the following

dropboxTeamClient.AsMember(account.TeamMemberId).WithPathRoot(new PathRoot.NamespaceId(account.RootInfo.RootNamespaceId))

Each user gives a different id for said Team Folder.

Greg-DB

If you're looking inside the same namespace shared across different accounts, the file/folder ID for any given file or folder inside the namespace should be consistent across accounts. Likewise the team_folder_id or shared_folder_id should be the same.

If you're looking at the mount point of any particular namespace such as team folder itself though inside different roots, the "id" (which identifies the place where the namespace is mounted in that root) would be different, while "shared_folder_id" should be the same.

If something isn't working as expected though, please share the rest of the relevant code and the output so I can take a look at what values specifically you're looking at. Thanks!

awb

Hi @Greg-DB

I'm currently reviewing the logs for a customer of ours, is it ok to share folder ids in the forum?

We currently us the following to list folders/files in a team folder

var account = dropboxTeamClient.AsMember(teamMemberInfo.Profile.TeamMemberId).Users.GetCurrentAccountAsync()

dropboxTeamClient.AsMember(account.TeamMemberId).WithPathRoot(new PathRoot.NamespaceId(account.RootInfo.RootNamespaceId))

dropboxTeamClient.AsAdmin(account.TeamMemberId).WithPathRoot(new PathRoot.NamespaceId(account.RootInfo.RootNamespaceId)

and then process the child folders

I have the id of the folder in our logs which I can no longer locate in dropbox, both using asadmin and asmember returns a not found. This id looked to be assocaited to a team folder, which is why I asked the question about team folder ids changing.

Is there anyway to locate this folder when I have the ID?

Thanks

Здравко

@awb wrote:
...
Is there anyway to locate this folder when I have the ID?
...

Hi @awb,

Did you try GetMetadataAsync method with your ID? If not, give it a try. Does this call return something meaningful or an error? If error, what error? 🧐

Hope this gives direction?

awb

thanks @Здравко , just given that a try and get not found. Tried looping through users and admins

dropboxTeamClient.AsAdmin(account.TeamMemberId).WithPathRoot(new PathRoot.NamespaceId(account.RootInfo.RootNamespaceId)).Files.GetMetadataAsync

dropboxTeamClient.AsMember(account.TeamMemberId).WithPathRoot(new PathRoot.NamespaceId(account.RootInfo.RootNamespaceId)).Files.GetMetadataAsync

UPDATE, its a deleted folder @Здравко thanks. Still need to get my head around what has been going on in this customers Dropbox.

Здравко

@awb wrote:
... Tried looping through users and admins
...

... and? 🤔 What is the result? You didn't mention. If result, what's it, otherwise, what's the error?

awb

If I included deleted items in the request, the item is returned. In my orginal requests I did not include deleted items.

Greg-DB

I see Здравко already offered some helpful guidance so it seems like you have this sorted out, but let us know if you still need help with anything.