Hi @rafAdobe , presently only out of the box connectors are available to use. Not sure on destination but No way to build your own custom source connector. However very soon AEP will have this feature [Self Source Connector Framework] so that one can build and publish their own connector. Post relea...

Hi @navink386520 ,dataset id has to be part of request body not as request parameter.  '{ "datasetId": "{DATASET_ID}", "inputFormat": { "format": "json" } }' Attaching postman snapshot..    

Hi @kmalkari1,  Profile + event data export in same export for same destination ? My take is No and array anyways you can see clearly its not supported.   What profile/event data export AEP support, It is highly depend upon destination type you're selecting to export profile data or an event data to...

Hi @Sneha-Parmar ,I would like hear from Adobe experts as well but here is something that I had personally built externally to create offers in AEP ODS.ODS offers apis for you to define your offer and its components. I had worked on a requirement where I had to build bulk offers & rules. Hence I had...

Thanks @Danny-Miller

Hi @NimashaJain , yes its resolved. CSV file don't accommodate array values hence AEP behaved as it should i.e overwriting existing value with latest one as it was a profile data.

How is self source connector framework different than building your own extension in adobe launch/data collection in terms of publishing process specially ? Is it more or less similar ? 

Which is that place where I can define an icon for my connector ? 

I'm not sure on practicality but I'm curious to know if we can have a connector without Auth spec?  Just thinking of a source which has some industry test data and connector is open to anyone who want to bring that test data into AEP and try some hands on ? 

While ingesting data specially from source like snowflake what I spotted is it doesnt list the schema details of snowflake to which table belongs to. We've been into a situation where table having same name under different schema was tough to distinguish. Its good to have path details of source tabl...