On giving it a second look, I noticed that you are using the attribute path from the schema, where as you should be using the path of the attribute in the incoming payload. The path that you shared seems to be the destination path and not the source path. Sorry if I misunderstood the question here.

Hello, You should be able to handle the PII and the other sensitive data using the out of the box labels. please take a look at https://experienceleague.adobe.com/docs/experience-platform/data-governance/labels/reference.html?lang=en  

In my case, I never have to prefix the attribute path with “xdm”. Also, there are no slashes in the path. But since you said that this path is working in the non-calculated mapping, I’m surprised. When writing the expression, instead of manually writing the attribute name can you use the attributes ...

Hello, we have a requirement to keep the data in two datasets in sync. For some reason, we can't ingest the same payload in both the datasets. We are planning to leverage the scheduled query service for this. For the incremental approach, I think snapshot clause is the way to move forward. However, ...

@Anil_Umachigi  WebSDK:  https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/tags-configuration/validate-with-debugger.html?lang=en https://experienceleague.adobe.com/docs/experience-platform/collection/e2e.html?lang=en#installServer API:https://experienceleague.adobe.com/docs/e...

@arijitg Yes, I have used the edge merge policy. I am even able to create edge segments based on that.

Hello,   We are working on edge segmentation. Our use-case requires both the server API as well as the web SDK for the edge data collection. My understanding was that the edge segments should get computed on the edge server and we should get the segmentMembership in the response to the interact call...

Thanks, @adobechat!   I tried using the msgType: xdmEntityUpdate. It seems to be deleting all the fields that are already there in the entity but not sent in the payload. I mean, it's behaving like a PUT instead of a PATCH.   Also, my use case is to send raw data and not XDM-compliant data. I am sor...

Hello,   We have a requirement to update the b2b_opportunity data using the HTTP API Source. It seems that there are two ways to do it:1. Include the payload header "msgType". Both the allowed values (xdmEntityCreate, xdmEntityUpdate) actually overwrites the data and thus we always need to send the ...

Hello All,   We have a situation, where the datatype of one of the schema attribute changed from string to array of string. The schema is not enabled for profile. We made the changes. But I see that the ingestion is still failing because of type mismatch. It's still seeing the schema attribute type ...