Hi @debanjanab15925 , I would suggest to use Adobe debugger extension and also establish a session between App and mobile sdk with data collection "Assurance" to troubleshoot the issue.
Hi @MichaelJo13 certainly its not best practice.I'm sure error message that you're getting is something like during data ingestion is ,"The message can’t be validated: [#/_field_path: expected type: String, found: Null]" despite the field not being required. The value null is not accepted/supporte...
Hi @vinayababu ,As best practice customer details always should come from CRM system or any enterprise system that is responsible for storing user customer details. AEP identity service rely on identity value and its name space as its just a simple database that store this information and runs conso...
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...
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 ?
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...
One of the feature we greatly miss while ingesting data into AEP is decrypting it on the fly. Data prep allows to hash data but there is no way to decrypt it. Any thoughts on this ?