This section describes how to edit the DSN configuration and then authenticate and connect to SAS Xpt APIs.

DSN Configuration

You can use the Microsoft ODBC Data Source Administrator to edit the DSN configuration. Note that the installation process creates a both a user DSN and a system DSN, as described in Installing the Connector.

Note: The connector stores connection information in the Windows registry. To ensure that the connector can write to the registry, either run Power BI as an administrator or use a User DSN for your connection instead of a System DSN.

User DSN

Complete the following steps to edit the DSN configuration:

1. Select Start > Search, and enter ODBC Data Sources in the Search box.
2. Choose the version of the ODBC Administrator that corresponds to the bitness of your Power BI Desktop installation (32-bit or 64-bit).
3. Select the system data source and click Configure.
4. Edit the information on the Connection tab and click OK.

System DSN

Configure the system DSN the same way as the user DSN, except you will need to switch to the System DSN tab before performing Step 3.

If you're using Power BI's On-Premises Data Gateway with Standard mode, you must use the system DSN.

You must also specify a valid location for CredentialsLocation (a path where the MFA credentials file is locally stored).

This is because the Standard mode runs on service mode and can only access permitted locations, such as C:\Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway.

The CData Power BI Connector for SAS Xpt allows connecting to local and remote SASXpt resources. Set the URI property to the SASXpt resource location, in addition to any other properties necessary to connect to your data source.

Connecting to Local Files

Set the ConnectionType to Local. Local files support SELECT.

Set the URI to a folder containing SASXpt files: C:\folder1.

Connecting to Cloud-Hosted SAS Xpt Files

While the connector is capable of pulling data from SAS Xpt files hosted on a variety of cloud data stores, INSERT, UPDATE, and DELETE are not supported outside of local files in this connector.

If you need INSERT/UPDATE/DELETE cloud files, you can download the corresponding CData connector for that cloud host (supported via stored procedures), make changes with the local file's corresponding connector, then upload the file using the cloud source's stored procedures.

As an example, if you wanted to update a file stored on SharePoint, you could use the CData SharePoint connector's DownloadDocument procedure to download the SAS Xpt file, update the local SAS Xpt file with the CData SAS Xpt connector, then use the SharePoint connector's UploadDocument procedure to upload the changed file to SharePoint.

A unique prefix at the beginning of the URI connection property is used to identify the cloud data store being targed by the connector and the remainder of the path is a relative path to the desired folder (one table per file) or single file (a single table).

Amazon S3

Set the following to identify your SAS Xpt resources stored on Amazon S3:

• ConnectionType: Set the ConnectionType to Amazon S3.
• URI: Set this to the bucket and folder: s3://bucket1/folder1.
  • You can also connect to SAS Xpt resources stored on Cloudera Ozone, after creating a volume and bucket and making a symbolic link to that bucket: s3://linktobucket

See Connecting to Amazon S3 for more information regarding how to connect and authenticate to SASXpt files hosted on Amazon S3.

Azure Blob Storage

Set the following to identify your SAS Xpt resources stored on Azure Blob Storage:

• ConnectionType: Set this to Azure Blob Storage.
• URI: Set this to the name of your container and the name of the blob. For example: azureblob://mycontainer/myblob.

See Connecting to Azure Blob Storage for more information regarding how to connect and authenticate to SASXpt files hosted on Amazon Blob Storage.

Azure Data Lake Storage

Set the following to identify your SAS Xpt resources stored on Azure Data Lake Storage:

• ConnectionType: Set this to Azure Data Lake Storage Gen1, Azure Data Lake Storage Gen2, or Azure Data Lake Storage Gen2 SSL.
• URI: Set this to the name of the file system and the name of the folder which contains your SAS Xpt files. For example:
  • Gen 1: adl://myfilesystem/folder1
  • Gen 2: abfs://myfilesystem/folder1
  • Gen 2 SSL: abfss://myfilesystem/folder1

See Connecting to Azure Data Lake Storage for more information regarding how to connect and authenticate to SASXpt files hosted on Azure Data Lake Storage.

Azure File Storage

Set the following properties to connect:

• ConnectionType: Set this to Azure Files.
• URI: Set this the name of your azure file share and the name of the resource. For example: azurefile://fileShare/remotePath.
• AzureStorageAccount (Required): Set this to the account associated with the Azure file.

You can authenticate either an Azure access key or an Azure shared access signature. Set one of the following:

• AzureAccessKey: Set this to the access key associated with the Azure file.
• AzureSharedAccessSignature: Set this to the shared access signature associated with the Azure file.

Box

Set the following to identify your SAS Xpt resources stored on Box:

• ConnectionType: Set this to Box.
• URI: Set this the name of the file system and the name of the folder which contains your SAS Xpt files. For example: box://folder1.

See Connecting to Box for more information regarding how to connect and authenticate to SASXpt files hosted on Box.

Dropbox

Set the following to identify your SAS Xpt resources stored on Dropbox:

• ConnectionType: Set this to Dropbox.
• URI: Set this to the path to a folder containing SASXpt files. For example: dropbox://folder1.

See Connecting to Dropbox for more information regarding how to connect and authenticate to SASXpt files hosted on Dropbox.

FTP

The connector supports both plaintext and SSL/TLS connections to FTP servers.

Set the following connection properties to connect:

• ConnectionType: Set this to either FTP or FTPS.
• URI: Set this to the address of the server followed by the path to the folder to be used as the root folder. For example: ftp://localhost:990/folder1or ftps://localhost:990/folder1.
• User: Set this to your username on the FTP(S) server you want to connect to.
• Password: Set this to your password on the FTP(S) server you want to connect to.

Google Cloud Storage

Set the following to identify your SAS Xpt resources stored on Google Cloud Storage:

• ConnectionType: Set this to Google Cloud Storage.
• URI: Set this to the path to the name of the file system and the name of the folder which contains your SAS Xpt files. For example: gs://bucket/remotePath.

See Connecting to Google Cloud Storage for more information regarding how to connect and authenticate to SASXpt files hosted on Google Cloud Storage.

Google Drive

Set the following to identify your SAS Xpt resources stored on Google Drive:

• ConnectionType: Set this to Google Drive.
• URI: Set to the path to the name of the file system and the name of the folder which contains your SAS Xpt files. For example: gdrive://folder1.

See Connecting to Google Drive for more information regarding how to connect and authenticate to SASXpt files hosted on Google Drive.

HDFS

Set the following to identify your SAS Xpt resources stored on HDFS:

• ConnectionType: Set this to HDFS or HDFS Secure.
• URI: Set this to the path to a folder containing SASXpt files. For example:
  • HDFS: webhdfs://host:port/remotePath
  • HDFS Secure: webhdfss://host:port/remotePath
  • Cloudera Ozone (via the HttpFS gateway): webhdfs://<Ozone server>:<port>/user/myuser
    • You must use Kerberos authentication to access SAS Xpt files stored on Ozone.
    • Ensure that you have Ozone 718.2.x on the Ozone cluster.
    • Cloudera Manager version 7.10.1 is required.

There are two authentication methods available for connecting to HDFS data source, Anonymous Authentication and Negotiate (Kerberos) Authentication.

Anonymous Authentication

In some situations, you can connect to HDFS without any authentication connection properties. To do so, set the AuthScheme property to None (default).

Authenticate using Kerberos

When authentication credentials are required, you can use Kerberos for authentication. See Using Kerberos for details on how to authenticate with Kerberos.

HTTP Streams

Set the following to identify your SAS Xpt resources stored on HTTP streams:

• ConnectionType: Set this to HTTP or HTTPS.
• URI: Set this to the URI of your HTTP(S) stream. For example:
  • HTTP: http://remoteStream
  • HTTPS: https://remoteStream

See Connecting to HTTP Streams for more information regarding how to connect and authenticate to SASXpt files hosted on HTTP Streams.

IBM Cloud Object Storage

Set the following to identify your SAS Xpt resources stored on IBM Cloud Object Storage:

• ConnectionType: Set this to IBM Object Storage Source.
• URI: Set this to the bucket and folder. For example: ibmobjectstorage://bucket1/remotePath.
• Region: Set this property to your IBM instance region. For example: eu-gb.

See Connecting to IBM Object Storage for more information regarding how to connect and authenticate to SASXpt files hosted on IBM Cloud Object Storage.

OneDrive

Set the following to identify your SAS Xpt resources stored on OneDrive:

• ConnectionType: Set this to OneDrive.
• URI: Set this to the path to a folder containing SASXpt files. For example: onedrive://remotePath.

See Connecting to OneDrive for more information regarding how to connect and authenticate to SASXpt files hosted on OneDrive.

OneLake

Set the following to identify your SAS Xpt resources stored on OneLake:

• ConnectionType: Set this to OneLake.
• URI: Set this to the name of the workspace, followed by the item and item type. Optionally, include the folder path to be used as the root folder. For example: onelake://Workspace/Test.LakeHouse/Files/CustomFolder.

See Connecting to OneLake for more information regarding how to connect and authenticate to SASXpt files hosted on OneLake.

Oracle Cloud Storage

Set the following properties to authenticate with IAMSecretKey:

• ConnectionType: Set the ConnectionType to Oracle Cloud Storage.
• URI: Set this to the bucket and folder: os://bucket/remotePath.
• AccessKey: Set this to an Oracle Cloud Access Key.
• SecretKey: Set this to an Oracle Cloud Secret Key.
• OracleNamespace: Set this to an Oracle cloud namespace.
• Region (optional): Set this to the hosting region for your S3-like Web Services.

SFTP

Set the following to identify your SAS Xpt resources stored on SFTP:

• ConnectionType: Set this to SFTP.
• URI: Set this to the address of the server followed by the path. For example: sftp://server:port/remotePath.

See Connecting to SFTP for more information regarding how to connect and authenticate to SASXpt files hosted on SFTP.

SharePoint Online

Set the following to identify your SAS Xpt resources stored on SharePoint Online:

• ConnectionType: Set this to SharePoint REST or SharePoint SOAP.
• URI: Set this to a document library containing SASXpt files. For example:
  • SharePoint Online REST: sprest://remotePath
  • SharePoint Online SOAP: sp://remotePath

    Use the Sharepoint URL as the remote path. Not the display name.

If your files are stored in a non-root-level SharePoint Online site (for example, under /sites/<your site>/), be sure to set the StorageBaseURL property to the full path of the SharePoint site.

• To access files in the top-level document library:
  • URI: Set this to sprest://Documents/
  • StorageBaseURL: Set this to https://<your domain>.sharepoint.com/sites/<your site>/
• To access a subfolder within that site:
  • URI: Set this to sprest://Documents/<subfolder>/
  • StorageBaseURL: Set this to https://<your domain>.sharepoint.com/sites/<your site>/

Using the full SharePoint site URL ensures the connector can properly locate files stored in non-root-level locations within your organization's SharePoint Online environment.

See Connecting to SharePoint Online for more information regarding how to connect and authenticate to SASXpt files hosted on SharePoint Online.

SharePoint On Premise

Set the following to identify your SAS Xpt resources stored on SharePoint On Premise:

• ConnectionType: Set this to SharePoint REST or SharePoint SOAP.
• URI: Set this to a document library containing SASXpt files. For example:
  • SharePoint On Premise REST: sprest://remotePath
  • SharePoint On Premise SOAP: sp://remotePath

    Use the Sharepoint URL as the remote path. Not the display name.

See Connecting to SharePoint On Premise for more information regarding how to connect and authenticate to SASXpt files hosted on SharePoint On Premise.