Campaign Management Tool Advanced Topics

 In this post I will call few of the basic of datasets in AEP. To start with here is the schema I created This is based on a custom class if Record Type (this class comes with one attribute Identifier shown as locked in the schema). I made the identifier as primary identity. Created a dataset with the same name as class. Data Loading 1. Delimitted File Created a simple delimitted file as below and created a workflow to load it into the dataset Sample Data: id,dataset_name,last_snapshot_id,process_timestamp,process_status,failure_reason journey_step_events_27878,journey_step_events,27878,2024-09-12T19:19:50.036Z,SUCCESSFUL,Not applicable aa_stitched_events_23451,aa_stitched_events,23451,2024-09-17T19:19:50.036Z,FAILED,There was no snapshot available journey_step_events_27891,journey_step_events,27891,2024-09-16T19:19:50.036Z,In Process,Not applicable 2. Using JSON Download the JSON format from the schma page and create JSON file using the format. For multiple records it needs to be ...

 Every time I have to add some advanced JS code inside Delivery I am confused about the sequence of JS. When it comes to Delivery, then there are multiple places where you can write the JS  Right Click on Delivery > Open > Go to Script Tab  Right Click on Delivery > Open > Go to Advanced Tab Typology Rule of type Control There are many phases where the rule will be run. I was trying to run the rule as much late as possible and thus had chosen "At the end of the analysis" Ignoring the option of adding JS code inside the Routing External account > Connector and Post processing workflow as I didn't run that Here is the result While the delivery is waiting at "Approve Targeting" , the log for the recurring delivery activity at workflow level looks like below The delivery log looks like below for the Typology Rules Note: At this stage the broadlog is not created and that makes sense as the Targeting is not approved yet While the  delivery is waiting at...

 I had many scenarios where I ran a costly query to select some good no of records and then process them further. But when it comes to processing I had to restrict the number of records to be processed in one go. And once the subset is processed, then select from the table again and then process the subset. Something like below where the end activity calls the signal when the complement from Split has more than 0 records to start the whole process again. But the problem is every time you have to run the costly select process to process a fraction of the records. As a result the overall throughput is decreased heavily. As an alternate I used a looping through the selected records avoiding selection every time I need to process the subset. Here the JS Activity after select is dummy one but required. I added a log in it with count. Test activity is also needed to ensure we have the exit path from the loop. In the above example the select query fetched 8680 records and then split restr...

The SQL Generated by Campaign created the string column with 255 chars like sFieldName VARCHAR2(255 CHAR) or similar depending on the the SQL type. So even if you need to store a field that requires bigger length, it  fails. The below trick I applied into a Campaign Standard implementation, but the code example is using Campaign Classic as I currently don't have access to the standard instance. In my case I had to create a calculated value which requires more than 255 char in length and it was complaining due to the length of the field. My ACC DB is Oracle and here is the error I got. ORA-210000 Oracle error: ORA-12899: value too large for column "AC_APPUSER"."WKF12862341_31_1"."SEXPR1676832221" (actual: 276, maximum: 255) Resolution: AC Standard Code: Read Option Variable: Add a field in Enrichment or Select Activity Additional Data using the expression $(options:<Name of the Option Variable>). Example: $(options:MyAPIKey)

 As we all know, the max value for any auto primary key field in Adobe is limited by the max of int which is 2.15B [[+/-) 2,147,483,647]]. As ACC doesn't support bigint as the auto pk column data type, you have to recycle the number every time it reaches near to that 2.14B mark.  Now Broadlog tables being the most heavily used table in ACC, we observe the issue often with this table but this can happen with other tables as well like Tracking and so on. It is not difficult to recycle the value of the sequence in ACC, but most of the time the BL and TL data is shared with downstream systems. So, once you reset the sequence, you have to make sure the downstream system knows about it and handle it properly without overwriting the existing historical records. And that is where these types of challenges are faced How do we inform downstream when ACC is resetting its sequence If downstream is managing the uniqueness of the records, then they have to prefix something to make sure it i...

 For one of the integration we had to do the base64 encoding using ACS and it was not that easy initially with the existence of the "MYTH" that ACS doesn't support JavaScript. Here is the code where I declared a class Converted inside a Content Block (it has to be block, not fragment) named "cbBase64EncodeLib" Note this process is only applicable if you have to use the encoded output inside email, it will not work if you need to save the value in a table <% var Converter ={         _keyStr : "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/=",         hexToBase64: function(hex) {             //var str = Converter.hexToString(hex);             //return Converter.base64Encode(str);             var hexStr = hex.toString(); //force conversion             var binary = "";           ...