Box Integration and Data Integration

First of all thanks for all your answers, your support is really really great (log is ok, hidden fields in email confirmation is ok...)

Question on box integration : 

We have already folders on box.com with customer name.

Under our architecture, it is located in folder box desktop/clients/customer name

How can we easily link the box folder with the destination folder of the files uploaded in the form and avoid any mismatch  ? (for example : a new folder for the same customer duplicated or docs uploaded in the wrong folder because the name of the customer is a common name and we have 3 of them call M. Jones1, M. jones2 in our existing system ?

For the moment I created a "buffer zone" under listepieces/customer name where the files arrive. 

But it is a pity that we have to copy and paste them in the target final folder.

Question on data integration 

Can I integrate data in the form depending on the content of a field.

For example, having a table somewhere with some info on our customer (number of children, marital status) linked to the mail adress.

If our customer enter the email address, it populate the form with the above info (children and status)

Thanks !

Regarding your box integration, if you want to have a unique folder for each of your submission, I suggest that it is more appropriate to use the Submission ID as your subfolder to avoid same full name submission on the same folder. 

For more information regarding box integration, you can check this article: How to Integrate your Form to Box.

Regarding your data integration concern, unfortunately, it is not currently possible to retrieve data and  prepopulate form with these data based on the email entered by user. As a workaround, I suggest you take a look at this article: How to Save Forms and Continue Later. It allows user to save and submit form and come back to it prepopulated by previously entered data. I am not sure if it is applicable to your business flow, though. If you can give us more details on what you are trying to achieve with this, we might be able come up with appropriate workaround.