Regarding AEP Queries features. | Community
Skip to main content
November 7, 2022
Solved

Regarding AEP Queries features.

  • November 7, 2022
  • 1 reply
  • 2112 views

Can we use queries to fetch segment's all attributes in AEP ?.

and I also find some auto suggested table name in Queries like (segment_ingestion_dataset, segment_export_dataset)

where does it come from as there is no such dataset present with this names.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Anuhya-Y

@infyashu : These are system generated datasets, you can find these by enabling show system datasets from UI. 

 

Could you please elaborate  below question, what are you looking exactly. 

"Can we use queries to fetch segment's all attributes in AEP ?"

1 reply

Anuhya-Y
Community Advisor
Anuhya-YCommunity AdvisorAccepted solution
Community Advisor
November 7, 2022

@infyashu : These are system generated datasets, you can find these by enabling show system datasets from UI. 

 

Could you please elaborate  below question, what are you looking exactly. 

"Can we use queries to fetch segment's all attributes in AEP ?"

InfyAshuAuthor
November 7, 2022

Using API, I want to do below

  1. Get the list of profiles qualified in a segment.

  2. Delete a specific profile from this list.

  3. Fetch the record details of the profile.

 

InfyAshuAuthor
November 10, 2022

@infyashu  check out below details.

 

Get the list of profiles qualified in a segment.

Note: replace profile_snapshot_export dataset name, segment id in the query as per the system you are using

Delete a specific profile from this list.

Fetch the record details of the profile.

Note:replace profile_snapshot_export dataset name, column name in the query as per the system you are using

 

 


On your third note of above reply i.e.

Fetch the record details of the profile.

 

I am able to fetch the details of single profile using select query but when I try to delete a profile using delete query

It is throwing an error (ErrorCode: 42601 Syntax error encountered. Reason: [Invalid command!])