First of all, the permission ContentHubGDrive
is actually the permission Files Connect Cloud
(hat tip to @DanielBallinger Mappings Between Salesforce Permissions)
The target org of the deployment does have Files Connect
enabled
However, the running user of the deployment does not yet have Files Connect Cloud
permission as that permission is embedded with the permission set being deployed and hence obviously hasn't yet been assigned to the running user in the target org (Catch 22).
The error message is misleading as it is not an org permission but is really a running user permission that is missing.
Action:
- Create a Permission Set called
Files Connect
, enable Files Connect Cloud
within the permission set
- Deploy that permission set to the target org
- Assign the running user that does deployments to the
Files Connect
permission set.
- Deploy the External data source and its associated custom object plus whatever else is part of your deployment package (auth provider, custom tab, etc)
Notes
Presumably, a similar error occurs for the other Files Connect data source types such as:
Files Connect: Box
Files Connect: Microsoft Sharepoint
Files Connect: Microsoft OneDrive