rossbelmont

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>AuthProvider</name>
    </types>
    <version>50.0</version>
</Package>

rossbelmont

{
  "columns": {
    "pk": {
      "filter": "categories#%",
      "values": [
        {
          "definition": "\"categories#\" + TEXT(category)"
        }
      ]
    },

rossbelmont

{
  "tableLocation": {
    "catalog": "AwsDataCatalog",
    "database": "works_of_art"
  },
  "tableName": "artwork",
  "extendedQualifiers": {
    "workgroup": "primary"
  },
  "keyColumns": [

rossbelmont

{
  "tableLocation": {
    "catalog": "AwsDataCatalog",
    "database": "mydb"
  },
  "tableName": "works_of_art",
  "extendedQualifiers": {
    "workgroup": "primary"
  },
  "keyColumns": [

rossbelmont

{
  "columns": {
    "fullName": {
      "virtual": "true",
      "values": [{
        "definition": "FirstName+\" \"+LastName"
      }]
    }
  }
}

rossbelmont

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Assign_Rating</members>
        <name>QuickAction</name>
    </types>
    <types>
        <members>privateConnectDemo2022022402</members>
        <name>OutboundNetworkConnection</name>
    </types>

rossbelmont

rossbelmont

Minimal IAM Permissions • Salesforce Connect adapter for Amazon Athena

The following represents a configuration of minimal IAM permissions needed to support the Salesforce Connect adapter for Amazon Athena. Specifically, this example uses a separate (dedicated) workgroup for Salesforce Connect to use with Athena, as well as specific S3 buckets containing the relevant source data.

This limits access to business data while providing enough access to metadata to make configuration easier for administrators. Note the following items in ALL_CAPS that will need to be replaced in your configuration:

• ACCOUNT_ID: ID of the AWS Account containing all the above resources (e.g. 467032906895)
• AWS_REGION: Geographical region containing the S3 bucket used by the workgroup (e.g. us-east-1)
• BUCKET_1_NAME: name of the S3 bucket used to house the source data
• BUCKET_N_NAME: included for instructional purposes in case Athena reads from multiple buckets
• RESULTS_BUCKET_NAME: name of the S3 bucket used by

rossbelmont

Potential bug in the Metadata API

Here's a note from one of our customer-facing architects:

I'm trying to load external credentials as metadata. Apparently, I can not push metadata that has a perm set and header all at once. I have to delete the perm set from the metadata for it to work. If I then resubmit the original metadata, it’s successful.

I have to do it twice, which is a bummer — deployment fails and I have to manually intervene.

rossbelmont

.DS_Store