hi @SantoshRa5  We have just done it in the past by updating the display name to have the prefix of "Do Not Use-"

Hi @god_prophet If you are just trying to activate down to AC Classic, the native connection should be enough. If you require more of a custom solution, you may want to go the s3 path. 

@SantoshRa5 As of now, this is still not possible at the schema level. We can disable the datasets that feed the schemas, but the schema itself can only be marked as un-usable

Hi @GigiCotruta  I can't find the exact documentation, but I believe you'll have to add the permissions to write to the dataset via the Admin Console. There should be an option to manage datasets within the product profile if i'm remembering correctly.

Hi @Michael_Soprano I believe the answer to this is yes, but it may not be recommended. If the merge policies are different - the population of Audience A may not align with that of Audience B from my understanding. Causing potential stitching issues.

Hello @jayasekar  You can use the flow service API to retrieve the details of the destination. These details will give you all segments that are currently being exported via that specific destination. Is this helpful?Flow Service API - Destinations

@itsMeTechy Yes they are case sensitive. We have seen this issue also with guids duplicating in all uppercase.

@Pradeep-Jaiswal  Sample profiles are based off of the sample job runs. Here is some more information on how this works Preview Sample Status (Profile Preview) API Endpoint | Adobe Experience Platform

Hi @Pradeep-Jaiswal   I don't believe there is any API that can directly filter the dataFlows pointing to each dataSet. I don't know of any quick hacks within the UI since UI has very limited filtering.

Hello @ButhpurKiran  You can accomplish this by exporting that audience to an S3 bucket and extract the file. Although, this will not export exact profiles, but the identity value that you choose to export.