Hi,
Client has multiple sub-businesses (about 4 or 5) and was earlier bringing in 1-Business data into AEP RTCDP. Then, very recently client wanted to bring in 2nd Businessses data. To do that I updated the exisiting schema as per client request and added fields which for 2nd Business.
For data Ingestion, I used exisiting Scheduled daily dataflow and added 2nd business or new fields into it. And created another dataset which had Schema PK + 2nd business fields to do a one-time load to bring in historical data for 2nd business. Client also wanted to use this data in CJA, due to two datasets and very less overlapping data between then, it will be an issue.
To fix this, I have two approaches,
Please let me know the correct and best approach.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hello, @SahuSa1,
Could you please clarify this part: "Client also wanted to use this data in CJA. Due to two datasets and very little overlapping data between them, it will be an issue."? It's not entirely clear what your question is.
That said, is the dataset (DS) you used for the second business enabled for profiles? If so, deleting it will also remove all associated profile data.
For a one-time load, I recommend ingesting everything into a dataset that is not profile-enabled first. Then, use a query to transfer the data to a profile-enabled dataset, ensuring it adheres to the XDM schema of the target dataset. This approach allows you to safely delete the non-profile-enabled dataset afterward.
Let me know if you need further clarification!
Views
Replies
Total Likes
Hello, @SahuSa1,
Could you please clarify this part: "Client also wanted to use this data in CJA. Due to two datasets and very little overlapping data between them, it will be an issue."? It's not entirely clear what your question is.
That said, is the dataset (DS) you used for the second business enabled for profiles? If so, deleting it will also remove all associated profile data.
For a one-time load, I recommend ingesting everything into a dataset that is not profile-enabled first. Then, use a query to transfer the data to a profile-enabled dataset, ensuring it adheres to the XDM schema of the target dataset. This approach allows you to safely delete the non-profile-enabled dataset afterward.
Let me know if you need further clarification!
Views
Replies
Total Likes
Hi @GigiCotruta , Thanks for your reply.
Let me clarify the "little overlapping data" point. We used two datasets-
Could you please provide me with any documentation link, that you may have handy for achieving the ingest via Query service.
Thanks,
Sambit
Views
Replies
Total Likes
You probably need this docu: SQL Syntax in Query Service | Adobe Experience Platform
SELECT
_ELCORTEINGLES.CO_PAIRWISE AS CO_PAIRWISE,
ARRAY_AGG(
STRUCT(
_ELCORTEINGLES.AUDIENCES.CO_TRATAMIENTO AS CO_TRATAMIENTO,
_ELCORTEINGLES.AUDIENCES.DT_INICIO AS DT_INICIO,
_ELCORTEINGLES.AUDIENCES.ID_AUDIENCIA AS ID_AUDIENCIA,
CASE
WHEN _ELCORTEINGLES.AUDIENCES.ID_AUDIENCIA = '8889' THEN 'Eci audiencia 2'
ELSE _ELCORTEINGLES.AUDIENCES.NA_AUDIENCIA
END AS NA_AUDIENCIA,
_ELCORTEINGLES.AUDIENCES.NA_TEXTO_1 AS NA_TEXTO_1,
_ELCORTEINGLES.AUDIENCES.NA_TEXTO_2 AS NA_TEXTO_2,
_ELCORTEINGLES.AUDIENCES.NA_TEXTO_3 AS NA_TEXTO_3,
_ELCORTEINGLES.AUDIENCES.NA_TEXTO_4 AS NA_TEXTO_4,
_ELCORTEINGLES.AUDIENCES.NA_TEXTO_5 AS NA_TEXTO_5,
_ELCORTEINGLES.AUDIENCES.TS_TACADA AS TS_TACADA
)
) AS audienceECI
FROM
audiences
This part of the query is made for this part of the Schema:
Thanks @GigiCotruta
Views
Replies
Total Likes
Views
Likes
Replies