Box for Salesforce - FAQs

The following article addresses some frequently asked questions about the Box for Salesforce integration.

 

FAQs

What type of Salesforce license does Box for Salesforce support? 

Box for Salesforce currently only supports the following license type:

Standard User Licenses: Salesforce

This license type can and does frequently use custom objects in addition to the standard CRM objects. Custom objects have always been supported and that should never change.

 

Do I need to migrate my data if I upgrade to the new integration?

Yes, you must migrate your data before using the new Box for Salesforce integration. Two main differences between the older version and the new version require a migration:

 

  • Updated folder structures: The new integration uses sub-folders for each object (Opportunities, Accounts, etc.). This is different from the flat folder structure in the older integration.
  • Associated metadata: The new integration stores metadata (partially for records and in a table) for associated folders, shared links etc., on Salesforce. The older version added partner tags to the Box folder.

 

Does the Salesforce admin also need to be the Box admin for the integration to work?

For the Box for Salesforce integration to work, a service account (a Box account with Admin or co-admin privileges at a minimum, dedicated to the Salesforce integration) must be tied to the Box for Salesforce integration. See the Box for Salesforce User Guide for more details on integration prerequisites.

 

Does the integration automatically create folders for all Salesforce objects e.g., Accounts, Leads and Opportunities?

Not automatically. To start, the Salesforce admin will need to add Box Embed to object record page layouts. Then, a user has to navigate to a specific record page and, within the Box Embed framework, confirm that they want to include content in Box for this record. Some Salesforce records might have an associated Box folder while others do not.

 

Does the Box interface support custom Salesforce objects?

Yes, for custom objects you can build your own Visual Force pages. See the Box for Salesforce User Guide for instructions.

 

If a user renames an opportunity folder on Box, what happens to the Salesforce record?

Objects are linked by the tags in Box, which refers back to the Salesforce object ID. This means the Salesforce record name remains unchanged, but the embedded Box content will reflect the new folder name.

 

What happens when a lead is converted to an opportunity?

The Box for Salesforce integration allows the Salesforce admin to determine if a folder should be moved or remain as is. In either case, the opportunity links to the correct folder.

 

Does Box for Salesforce support seamless logins?

Yes. Box for Salesforces uses OAuth2 to connect to Salesforce with a dedicated Box account.

Box for Salesforce automatically logs the user into Box if the seamless login feature is enabled.

 

How does Box for Salesforce work on mobile devices?

Mobile cards for Salesforce (formerly known as Salesforce1) are provided for standard objects. These mobile cards redirect users to m.box.com, which provides mobile access to all of your content either on a browser or the Box application (if installed).

 

What restrictions can an admin place around Salesforce content in Box?

The user's Box permissions are determined by permissions in Salesforce.

  • Read/Write access on Salesforce translates to an Editor role on Box.
  • Read-only access on Salesforce translates to a Viewer role on Box.
  • The Box for Salesforce integration ensures that all permissions are in sync.

When a user creates a Box folder for a Salesforce record, they are added as collaborators and, therefore, will only have access to this specific subfolder. A user will be able to see the folder path that leads to the record-specific folder without seeing any other content within those folders along the way.

 

See What are the different access levels for collaborators? for additional details on Box collaborator roles.

 

Does the integration support merging accounts?

The integration currently does not support merging accounts.

 

Are Salesforce communities supported?

No, Box for Salesforce currently does not support Salesforce communities.

 

How can I customize the Box for Salesforce integration?

Box offers a Salesforce Developer Toolkit that provides the ability to further customize the behavior of the Box for Salesforce integration programatically. The Toolkit consists of several global APEX methods that can be used to trigger and extend the default behavior: Box For Salesforce: Developer Toolkit

 

How do I uninstall Box for Salesforce?

Follow these instructions to uninstall Box for Salesforce:

  • If you have any Box pages added to page layouts, remove them.
  • If you have any Developer Toolkit customizations in your apex code, remove them.
  • If you have any references to the objects included in the Box for Salesforce packages in your apex code, remove them.
  • Uninstalling the appexchange app will not delete data in your box account but any associations between records/folders/users will be removed.
  • From Setup -> Build -> Installed Packages, choose Uninstall on Box for Salesforce.
  • To preserve any of the FRUP data, export if from your Salesforce instance first.  That data will get deleted once the package is deleted. will need to export it from theirsalesforce org first.  That gets deleted when the package is uninstalled.

Additional Information:

We look forward to receiving feedback about the installation process and the integration through Salesforce AppExchange.

 

Version history
Revision #:
28 of 28
Last update:
‎12-05-2017 08:51 AM
Updated by: