Hi @fernandac322631 , I share with you an Adobe doc link. You can do a workflow in order not to touch the file, following the next steps regarding activities:-Load file activity: It will load your file into a temporary table.-Enrichment: Here in the Additional data tab it will be necessary to ad a c...

HI @Shruti1, I share with you some useful documentation links:- Creating filters- Functions(Functions link, goes to Standard documentation but the majority of them can be applied to classic) Additionally, I give you a possible solution as a guidance, to solve your issue. Add it inside your schema un...

Hi @Shruti1, I share with you some useful documentation links to solve your issue:Schemas Schema reference  Besides I give you a solution as a guidance, creating a calculated field: <computedExpr expr="iBrandId == 0 ? 999999 : iEntityId"/> Regards, Celia 

Hi @Shruti1, In terms of doing the join conditions you can have a look at the following doc link. Inside your xml schema you can use this solution as a guidance:<join xpath-dst="@iEntityId" xpath-src="Iif(@iBrandId = 0, 999999, @iBranchId)"/> Regards, Celia   

Hi @Shruti1,  You can use the following documentation to help you to solve the issue: Filter creation and Sysfilter elementFor the creation, you should insert the filter inside the schema you want to apply it, editing its XML under (Administration>Configuration>Data Schemas). You can try this soluti...

Hi @SankarRa1,  You can use this documentation: jsapi-en Regards, Celia

Hi @NickMannion, So far what I know is that there is not a workaround that supports folder structures for reusing or organizing audiences. My recommendations for the projects that I have work until the moment for this, is to have a consistent naming convention that can help you to find the audiences...

Hi @AditiKaushik, You will need to define the relationship between your source schema and the lookup schema. Both of them will need to be Real Time Customer Profile -enabled, and the destiantion schema must have the lookup key set as primary identity. This can be done via API or the propper interfac...

Hi @Ragsthenos,  To add an addional column, you will need to extend the schema and then configure the display of the additional column. You can follow the next steps:1. Extend the schema (nms:recipient): Add the custom field that you want and be sure to save it and publish it after the modifications...

Hi @Shruti1, I share with you a useful documentation link, that can help you to clarify your issue. Try with these two options  inside the XML schema where you need the filter:A:<sysFilter> <expr> <![CDATA[ (@brand=0 and @branchId=999999) or (@brand!=0 and @branchId=table1.BRANCH_I...