[AC v8] New workflow activity: Change Data Source | Community
Skip to main content
Sukrity_Wadhwa
Community Manager
Sukrity_WadhwaCommunity Manager
Community Manager
August 9, 2021

[AC v8] New workflow activity: Change Data Source

  • August 9, 2021
  • 1 reply
  • 1419 views

In Adobe Campaign workflows, data is managed using working (or temporary) tables. As the workflow executes, working tables share data across workflow activities. By default, working tables are created on the same database as the source of the data we query on.

The new Change Data Source workflow activity allows you to change the data source of a workflow's working table. This provides enhanced flexibility in managing data across different data sources (FDA, FFDA & local database).

With Campaign v8, the main profiles table is stored on the cloud database directly. So querying on the Profiles table will create a working table on the cloud database as well. In certain cases, it can make sense to move the working table to another data source in order to perform specific operations.

Read here for more information: New workflow activity: Change Data Source

 

In case you have any questions, please feel free to post them below or reach out through the community Q and A section. 
In case you have any ideas and/or suggestions regarding the Campaign product, then kindly submit them here.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

P
pmchinchu
January 25, 2022

Hi Sukrity,

 

I'm trying to explore this new activity in V8 and while doing testing, I observed that the workflow is running without using Change data source activity. Below is the scenario that I was testing:

Created one schema in local and one in Cloud. Queried both schemas and intersected on email address field, which is the common field for both, keeping the primary set as cloud schema. The workflow ran successfully. 

But when I kept the primary set as local schema, it kept failing due to:

01/25/2022 3:07:08 AM union PGS-220000 PostgreSQL error: ERROR: COALESCE types integer and character varying cannot be matched LINE 1: ...yaltyBalance) SELECT DISTINCT Coalesce(Input1.iId,Input2.uId... ^ .

When do we actually need to use Change Data source activity? Can you help us understand this better.

 

 

Sukrity_Wadhwa
Community Manager
Sukrity_WadhwaCommunity ManagerAuthor
Community Manager
January 31, 2022

Hi @pmchinchu,

 

I have forwarded your Campaign v8 related queries to our experts and some one will soon get back to you on this. 

 

Thanks!

Sukrity Wadhwa
Terms & ConditionsAccessibility statement

Loading footer...