@ArunLa after installation did you follow the configuration documentation https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/commands/configure/overview as configuration and mapping required as well
yes, then maybe at ETL level/ prior ingestion change to data to string to avoid any additional data transformation at AEP as it has the limitation @bjoern__koth
consider below if works @kamil_tagging - Validate that the Edge Configuration includes the correct XDM schema and fields. - Data collection /Tag are published and implemented on site, on the environment ur testing - validate XDM mapping and data type for value - Use AEP debugged to see if any error ...
may be it not if used with WebSDK or segments are based on the https://experienceleague.adobe.com/en/docs/analytics/components/real-time-reporting/realtime
adding to the solution suggested by @arunpatidar - check log and error file - Clean dispatcher cache in case of dispatcher - check permission / env specific to author/publish?- if on the publisher, check the replication
@georhe6 it is depend on what is the case here if ask to have an author experience where the author can add/remove fields or update style the solution suggested by @BrianKasingli is good but if the ask does not have any author experience then the option without dialog can also work
consider below- if it is on another template, not the same template where the other working one is present then check if the template is published and accurate mapping - Go to /crx-quickstart/logs/error.log on the publish instance to inspect any errors related to the content fragments.- Does your ne...
It is recommended to set the JDK version for the entire Maven execution to 11 for Adobe Cloud Service projects, irrespective of SDK version, and remove/update Java 8 dependencies in the code base for Java 11 - if any present in code base