Saving CSV to box.com

Integrator.io
1

I've set up a connection to box.com, but I can't seem to figure out how to import a CSV file. There's an input for Directory path, but I just get an error saying Invalid Directory. The Provided directory does not exist.

I've created the folder at the root of my account and my account is the one the connection is using. The question mark tip says to enter a relative path, but doesn't say much more than that.

I currently just have it set to CeligoTest which I created in Box.

This is a box.com account managed by my company.

2

I just tested myself and All Files works, but All Files/something doesn't work. We are making api calls behind the scenes to get the folder id and for some reason Box is returning no results. When I make the same api call with a normal export, I do get results. I've raised this internally to see if engineering can see what's going on here.

3

Alright I figured out the bug and we'll get it fixed. There seems to be a caching issue. When I made a completely new import and put in the correct path the first time, it worked. So your path should be All Files/folder1/folder2.

4

Great, thank you for the help!

I wondered if the system was making multiple API calls since this didn't really line up with the Box API docs.

I had no idea I needed to specify All Files as the root folder. I understand this may be a Box thing, but it would be great to see this get mentioned in the field's tooltip.

I also noticed I had to refresh by browser tab to get it to refresh the sample/mock data from the previous step if it changed.

5

@tomsantiago and @stephenbrandt are already on top of getting the docs and help text updated!

1 Like
6

@tylerlamparter - Was this bug ever fixed? I am making my first connection to Box and was also unaware that the Directory Path needed to start with All Files/folder1/etc until I came across this post. If I have made an export already that didn’t work to Box, do I need to make a new export and re-enter the directory path according to All Files/folder1/etc to eliminate the cacheing from the first export?

7

I just checked the ticket, and it looks like this isn’t actually a caching issue—it’s primarily how Box behaves.

Here’s what happens in different cases:

  • Newly created directory – It takes about 10 minutes for Box’s API to index the new folder. Until then, both exports and imports will fail.

  • New directory with new folder/file added – Same behavior, it still won’t work until ~10 minutes have passed from when the folder was first created.

  • Deleted directory – This takes effect immediately, so exports/imports will fail right away.

Also, keep in mind: the folder path must be provided as

All Files/folder1/folder2

and everything in the path is case sensitive.

You can find more details on Box’s indexing delays in their docs here: Box Search Indexing Availability.