Adobe Experience Platform

We have a custom text block used across 100+ pages in AEM Edge Delivery Services.Our block structure is based on ordered JSON fields, and recently we introduced a new field in the block. Because of this, all existing row indexes shifted by one, and we updated our JS/decorate() logic accordingly.However, after deployment: The updated JS expects the new field order. Existing pages still render plain.html in the old structure/order. The new field is missing in the rendered output. modelFields/children count still reflects the old structure. If we manually edit and re-save a page/block (even a minor change), the block gets regenerated correctly: modelFields gets updated children count becomes correct new field appears in the front So currently it looks like all existing pages would need manual re-authoring/re-saving.One additional complication in our setup: We cannot safely add new fields at the end either. Our tabs are structured like overview + common. The common tab append

Hi Adobe Community, Greetings! For a certain use case, we were exploring options to create calculated fields from events source table and map it to a profile type schema. Will this work?In the events source dataset, there are fields which says what is the account type of the user, whether its active or not (Active flag), Identifier, etc.What we wanted to build in AEP was to create flag/boolean fields for a particular user, accounting for each account type. For ex - A user can have multiple accounts, say Savings account, Spending account, tax saving account, high returns account. What we want to create is 4 fields for each user. So the schema would essentially have Identifier + 4 account type fields.  Logic of each field-Identifier: would be mapped to Identifier. Savings Active: if Account type = Savings account AND Active account = True, then Savings Active field turns true else remains false.  Spending Active: if Account type = Spending account AND Active account = True, then Spending

We’re currently evaluating an enterprise API migration strategy for an AEM Cloud implementation and wanted to get input from teams that already went through something similar.Historically, our downstream AEM services relied on a middleware layer that handled:response transformation, field normalization, validation mappings, and compatibility logic for consuming components.Now that we’re moving closer to direct enterprise API consumption, we’re debating whether it’s better to:Introduce a transformation/adaptor layer temporarily to preserve compatibility for existing AEM services/componentsORRefactor all consuming services directly against the new API contractMain concerns are:scalability, long-term maintainability, regression testing effort, performance overhead, and dependency coordination across multiple teams.Would be interested in hearing how other enterprise AEM Cloud teams approached this tradeoff in production environments.

I am trying to add aria-label to rte link plugin. I have added it but its getting stripped even after adding the value to the xss protection config. How to solve this.

We have a non-XDM compatible dataset enabled for upsert with a couple of fields of type Object[].rootNode.fieldName: Object[]rootNode.anotherFieldName: Object[]We want to be able to edit one of them at a time and to replace the whole list on that update operation, including emptying out the list. On the dataflow mappings we have that field mapped asupsert_array_replace(rootNode.fieldName) -> rootNode.fieldNameWe were able to see full list replacements where the profile attribute had [A, B] and we sent [C] and it worked correctly becoming just [C].Our issue is that we couldn't clean the field from [A. B] to [] by sending [] or null, or anything else we could think of on the HTTP merge-enabled call.How can we clean an attribute of type list in that case?

We are exporting a CJA dataset from AEP to Azure Data Lake Storage Gen2 using the destinations connections in AEP. We have connected the account through the initial setup. However, we are receiving an error for the export job. We have confirmed the folder and path do exist and the account has all rights necessary to create the export. The documentation states: Folder path: Enter the path to the destination folder that will host the exported files.” We aren’t sure if this is an absolute path or relative path, but tried both. Any ideas?Error Code: ACTBTC-2400-400Error Message: An error has occurred when exporting data to the destination. Unable to perform the data export with the parameters flowId=45f4d5d5-62fb-4407-8c87-806a66e76015 datasetId=69a9f4aa23235bf67317dd6e flowRunId=550339e9-dded-431d-a115-47e4ef53afc5. The error message returned by the destination is An unsupported operation has been performed. The path may not be correctly specified.  

If the user is in two user groups:high level of access - edit  low level - view Which one has the priority? 

I had a question regarding reducing latency for data availability in Customer Journey Analytics (CJA).We understand that a latency of around 1–2 hours for data to become available in CJA is fairly normal. However, there is a requirement from the client side to have data available sooner, ideally within 15 minutes.One suggestion was to look into setting up a Streaming API to reduce the delay. From my understanding, the Edge Network to AEP/CJA setup already uses streaming ingestion, and based on Adobe’s SLA documentation, the processing time still appears to be within a similar timeframe.I’m aware that true real-time capabilities would require additional licensing/capabilities, which the client currently does not have. So my question is:With the existing AEP/CJA setup and licensing, are there any recommended approaches or best practices to reduce the latency and have data available sooner in CJA?Would appreciate any guidance from anyone who has worked on similar implementations.

We are trying to migrate our Snowflake authentication method to key/pair as recommended. We are following all necessary steps but still running into authentication error. Curious if anyone has done this lately and can share gotchas? 

Hi, I need to speak with an AEM cloud expert regarding a migration from on prem to cloud. Could you kindly get in touch with me. Thank you!. 

Hi Community, we are ingesting customer profile data into AEP via batch ingestion into a profile-enabled dataset. The batch runs show as successful in Monitoring and the data is visible in the dataset preview. However the Real-Time Customer Profile is not reflecting the updated attributes and our segment membership is not updating even after 24 hours. Identity stitching is configured with ECID as primary identity. We verified the dataset is profile-enabled and the schema has the correct union schema. Batch status shows as Success with no failed records. What could cause profile not to update even when batch ingestion succeeds?

A question that comes up frequently when working with shared Field Groups: does marking a field as Primary Identity in one schema affect other schemas using the same Field Group? And how do you handle required fields that don't apply to your specific dataset?These are two separate concerns that get conflated because they both live in the schema layer.Primary Identity is Schema-LocalMarking a field as Primary Identity is a local decision scoped entirely to that schema. It has zero upstream impact on the Field Group definition or any other schema using it.Identity designation and field group constraints are completely separate layers in AEP's Schema Registry:- Field Group = shared blueprint with structural rules (required, data type)- Schema = local implementation including identity role assignmentsField A stays required everywhere because that constraint is defined at the Field Group level. Field B being Primary Identity in Schema X doesn't change anything for other schemas.Handling Req

How is that possible? Or only Dev2 is on a prod?  

Hey team, I recently developed a data element to dynamically populate the datastreamID based on the page hostname - however the edgeConfigID is still resolving to %data element%. Any advice on how I can configure the data element so it is available at run time? Currently on Adobe Experience Platform Web SDK  v2.34.1 extension  In this thread it mentions that Adobe fixed the issue at the extension level , however I am encountering the same issue Thanks,Ty

Hi All, I’m looking to tidy up fields in our schemas that are activated for profile, and have been looking into field deprecation.  I fully understand deprecating a field doesn’t delete it, just removes it from the schema view, but I was also hoping it would clean it up from the profile view, audience builder…  Am I doing something wrong or is this by design and it will only be deprecated from the schema itself? Many Thanks, Paul

Hi, I need some help regarding an issue with our Adobe Experience Platform Web SDK and Adobe Target implementation.We are working on an integration using Adobe Launch, Web SDK (sendEvent) and Adobe Target, where everything works correctly on the initial page load. We already have a working setup where the Web SDK sends a request using correct decisionScopes, and a separate applyPropositions rule is used to render the experiences.However, we are facing an issue in a SPA environment where the page does not fully reload. Instead, filter changes update the URL using hash changes (window.location.hash).The problem is that when the user changes filters:the URL hash updates correctly but we cannot reliably trigger a new sendEvent the Launch History Change event is inconsistent sometimes it fires multiple times for the same filter change sometimes it does not fire at all depending on navigation flow As a result, the Web SDK request is not consistently sent, and in some cases we do not receive

What conditions need to be met in order to set up one to many relationship?It has to be experience event schema?  

I want to ingest data for orchestrated campaign: Should I enable dataset for Campaign Orchestration after or before ingestion? Using Data Landing Zone  Can I use JSON , CSV ??? Why  I do not see that dataset while setting up dataflow?? 

It seems that a bug was introduce in version 2.34.2 of the AEP Data Collection Tags AEP Web SDK extension, whereby the extension’s version number is no longer included in the xdm.implementationDetails.version value. Now the value is “__VERSION__+2.34.2”. In previous versions the value was like this “2.31.1+2.34.1”.This data has been helpful in attributing the root cause of observed issues in collected data back to a specific version of the AEP Web SDK extension. How do we go about getting this bug fixed?

Hi everyone,I’m working on a schema configuration and have run into a question regarding field group inheritance and Profile enablement.The Setup: I have a Custom Field Group containing Field A and Field B. Field A was marked as "Required" at the Global Field Group level (it appears as mandatory in every schema it is added to). In my specific schema, I have designated Field B as the Primary Identity. In most other schemas across our organization, Field A is usually the Primary Identity. The Question: If I enable this schema for Profile and begin ingesting data, will my local configuration (marking Field B as Primary) have any "upstream" impact on the Field Group definition? Specifically, will Field B suddenly become a required field for other schemas using this same Field Group?Also, since Field A is "Required" at the group level but is NOT my primary identity in this specific use case, is there a recommended way to handle this during ingestion if Field A values aren't the focus

Hi Community,I'm looking for guidance on handling datetime values in Adobe Experience Platform where the source data is in local datetime but AEP's datetime datatype only stores values in UTC.The scenario:We ingest event data that includes timestamps originally in local datetime. Since AEP schemas require the datetime datatype to be in UTC format, the local time context is lost upon ingestion.However, when we use this data downstream for example, in personalization templates or email rendering we need to display the datetime back in the original local datetime format for the end user.My questions: Dual storage approach — Is it a recommended practice to store both a string field (preserving the original local datetime as-is) and a datetime field (in UTC) in the schema? This way, the string field can be used for display purposes and the datetime field for any time-based logic or segmentation.  Conversion functions — Are there any built-in helper functions that can convert a UTC datetim

Hello all,I want to re-ingest on data again for one of the failed batch. I have corrected the payload json but still getting an error and not succeeding with the batch re-ingestion. Can someone help me with is there any guideline to preparing the payload json, please help me.Is there any option to validate payload json in AEP itself before re ingesting it.Error details: There were errors encountered while parsing, converting, or validating the data. Please enable error diagnostics and ingest data again to preview or download an error log.Thanks,Kishore

Hi all, I’m currently trying to use the calculated field function in Data Prep to write logic for marketing channels, based on different URL parameters. However, I’m struggling with the syntax the interface is expecting, it seems to be semi SQL based but Adobe’s documentation is unclear around what the expected syntax should be.I’m trying to use the iif function to build out the logic, such as:iif(web.webPageDetails.URL LIKE ‘%di-social%’, "Social ",iif…Has anyone else used calculated fields for a similar purpose? Or are familiar with what syntax is expected for using nested iif statements?

I had the pleasure of speaking at an Experience League Community AMA at Adobe Summit this year, and I wanted to bring the conversation here for those who couldn’t make it. This is the kind of thing I genuinely wish someone had told me before we started.AEP on AWS  - Summit AMA RecapThe ContextWhen we set out to implement Adobe Experience Platform (AEP), the working assumption was that it would behave like any other cloud deployment. It didn’t. AEP’s defaults around networking, identity models, and tooling integration had been built against a specific cloud environment. That wasn’t documented anywhere, it was something you discovered by running into it. In our case, we discovered it during an architecture review, well into the project, not in a test environment.On top of that, Real-Time CDP and Customer Journey Analytics had to go live at the same time. That meant every foundational decision from schema design, identity resolution to data integration had to be right for two production s