■Background
When creating a folder on Box from Box for Salesforce, an error may occur.

However, due to the following error content, it is not possible to determine what caused the error.

【Text currently displayed as an error】
Sorry, there was an issue with processing this request.
Unable tp create a box folder for this record:
Unable to create folder for record id a0B2xAMOxEAK
- Details : Folder object returned from Box was null.

Can not proceed.

■Request
Please be more specific about the error.
e.g. "Contains characters that are not available in the Box".

■背景
Box for SalesforceからBox上にフォルダを作成する際、エラーが発生することがあります。

しかしながら、以下のようなエラー内容のため、何が原因でエラーが発生しているのか判別できません。

【現在のエラー内容】
Sorry, there was an issue with processing this request.
Unable tp create a box folder for this record:
Unable to create folder for record id a0B2xAMOxEAK
- Details : Folder object returned from Box was null.

Can not proceed.

■ご要望
エラー内容を具体的に記載して欲しい。
例）Boxで利用できない文字が含まれています 等

In the current Box for Salesforce integration, Box Admin can't limit the Salesforce tenant which can be integrated and Box for Salesforce integration can be setup with normal Box accounts so normal employee can set up Box for Salesforce by using their normal Box account and Salesforce Developer edition.

Even if the company prohibit to access Box from a private computer from home or outside the company network, once this integration was setup and access token was give to Box for Salesforce application a user can retrieve the contents via Box for Salesforce from a private computer.

So this can be security hole and we want Box to fix this problem. And if we can limit the Salesforce tenant which can be integrated to only the one Box Admin allow in the Box Admin console, I think this issue can be cleared.

We would like to put some information of DocuSign Envelope (such as contract data, term of contract, type of contract etc.) into Box metadata instance in an automated way. Currently, there's two ways users would be able to do are; 1. users manually populate metadata such as transaction amount in signed document or 2. using iPaaS (Workato) to automate populating metadata. No.1 is inefficient and time-consuming and has human-error risk. No.2 requires additional cost. This is actually required by Japanese local law when we save financial documents digitally. The law is called Denshi Chobo Hozon Hou. This becomes a huge roadblock for box/DocuSign customers to implement/adopt both systems for use-cases associated with saving signed financial documents in Box.

For the law of Denshi Chobo Hozon hou (https://www.nta.go.jp/law/joho-zeikaishaku/sonota/jirei/05.htm), please find the google-translated excerpt below

Requirement 5
Ensuring search function Article 3, Paragraph 1, Item 5 of the Enforcement Regulations
Secure a search function that meets the following requirements for electromagnetic records related to books
(B) The main record items according to the transaction date, account, transaction amount, and other types of books can be set as search conditions.
(B) For record items related to dates or amounts, conditions can be set by specifying the range.
(C) Conditions can be set by combining two or more arbitrary recording items.

Box support needs to address this error immediately.

Currently, Teams Private Channels are not supposed to have the ability to add the Box app. The behavior we've seen is that if the private channel already exists prior to adding the Box app to the Teams group, the Box app gets added to that private channel as well where it auto creates a Box folder. It works if private channel is added after Box app has been added to the Teams group.

The response I got from Box support is that they are planning to eventually integrate the Box app in private channels.

In any case, Box for Teams Permissions seems to be adopting the top level permissions from the Teams group level is posing a high security risk to the permissions that should only be allowed to private channel users. Users from the same Teams group can access the private channel folder created in Box and can modify anything.

Since Box won't fix the auto-creation of folders from a private channel, Box will need to auto-identify to only allow the permissions to select users for the Box private channel folder that was auto-created.

Three times in the last two months, we have lost hours of edits to box files made in PowerPoint Online. Box’s position is that this is a communication failure on the Microsoft side: box passed the file to Microsoft and Microsoft failed to pass the file back. The edits made are lost with no recovery possible.

Since Microsoft has published its auto-save frequency for all of its integration partners (see https://wopi.readthedocs.io/en/latest/scenarios/coauth.html), could box implement a process to check for the auto-save in the window specified by Microsoft, and alert the end user if it’s not occurring? If box sees widespread failures, box could include it in the list of known issues on its website. Since box is not checking to see if files are auto-saving, it has no way of knowing when the issue is occurring as it did after a Microsoft break fix on July 23-24.

It would certainly seem that box is better equipped to do this than an end user who has no visibility into the communication between box and Microsoft or lack thereof.