Register a private listing for Workfront Data Connect

You can share your Workfront Data Connect data directly with your organization’s Snowflake account by registering a private listing. This connection method uses Snowflake’s private listing capability to securely share data between organizations without exposing it publicly, and it works across regions and hosting platforms.

A private listing is useful when you want to join your Workfront data with other data in your enterprise data warehouse. Because the data lands in your own Snowflake account, you can query it alongside the rest of your data.

Access requirements

You also need a Snowflake account with permissions to accept listings and create databases, and a Workfront Data Connect entitlement.

What a private listing shares

A private listing gives you access to the following:

Differences from a reader account connection

A private listing shares a different set of views than a reader account connection, and the data arrives on a different schedule. Keep the following differences in mind:

Register a private listing

To register a private listing, first gather your Snowflake account details, then add the listing in Workfront.

Gather your Snowflake account details

Workfront uses your Snowflake account details to target the listing to your account. Gather the following details:

Each of these values is available from the Account Details modal in Snowflake.

To find your account details:

Also decide on the name of the database you want to access your linked Workfront data through. You enter this name when you register the listing.

Add the private listing in Workfront

You register the private listing through the Adobe Workfront interface.

Connect to the listing in Snowflake

In your Snowflake account, establish a connection to the private listing as an external data source. You can then query your Workfront data alongside the rest of your data.

Set up Current and Daily History views

A reader account connection provides three data views for each object table:

A private listing shares the Event view only. This section provides SQL to build the Current, Daily History, and Event views in your own Snowflake account.

All of the event views included in the listing have the fields needed for the view logic below. These examples assume that you have created a new database and schema of your choice in the target Snowflake account, and they use the projects_event view. In each example, replace <listing_db> and <listing_schema> with your own values.

Current views

The Current view of an object is the last change event record stored in Data Connect. If the last record is in a deleted state, the record is omitted from the Current view. All event views have the same structure.

create or replace view projects_current copy grants
as
select *
from <listing_db>.<listing_schema>.projects_event
where end_effective_timestamp = '2300-01-01'::timestamp_ntz
 and nvl(deleted, 0) != 1;

The deleted and end_effective_timestamp columns aren’t necessary in the Current view. The view filters the data to a single value, and it removes the record completely if the record is deleted.

Daily History views

The Daily History view identifies the change event record that was active at 23:59:59 of a given date, so you can trend the record’s state over time. The following example gives the state of a project record at the end of each calendar day.

create or replace view projects_daily_history copy grants
as
select d.calendardate as
 , p.*
from <listing_db>.<listing_schema>.calendar_dates d
join <listing_db>.<listing_schema>.projects_event p
 on p.begin_effective_timestamp <= d.calendareodtimestamp
and d.calendareodtimestamp < p.end_effective_timestamp
where d.calendareodtimestamp < current_date() - 1
 and nvl(deleted, 0) != 1;

Event views

For consistency, we recommend that you create a copy of the event view from the listing database and place it in the same schema as your Current and Daily History views.

create or replace view projects_event copy grants
as
select *
from <listing_db>.<listing_schema>.projects_event;