Adobe Campaign Schema - Template vs Aggregate

While looking into the schema, I saw in some places we are referring to an element of a different schema instead of declaring it again and again. But in some places, it is done using template attribute and other places use aggregate attribute.
So to test, I though of using the element "auditTrail" declared inside the library xtk:common
The element is as as below

  <element name="auditTrail">
    <element defOnDuplicate="true" name="createdBy" template="xtk:common:createdBy"/>
    <element defOnDuplicate="true" name="modifiedBy" template="xtk:common:modifiedBy"/>
    <attribute defOnDuplicate="true" default="GetDate()" desc="Creation date" label="Creation date"
               name="created" type="datetime"/>
    <attribute defOnDuplicate="true" default="GetDate()" desc="Modification date"
               label="Last modified" name="lastModified" pkgStatus="always" type="datetime"/>
  </element>

I inserted the element inside one of my schema as below using both of aggregate and template
<element ...>
....
    <element aggregate="xtk:common:auditTrail" name="Audit" label="Audit using aggregate" />
    <element template="xtk:common:auditTrail" name="AuditTempl" label="Audit using template" />
 
  </element>

And here is the outcome. Aggregate doesn't add a grouping element with the label provided whereas template does.

Note, template attribute is used as an attribute of attribute declaration element as below too.
<attribute name="phone" template="nms:common:phone"/>

Here the template destination entity has to be declared as an element as below from the nms:common schema
<element dataPolicy="phone" desc="Phone number" label="Phone" length="32" name="phone" type="string"/>

Refer to: Adobe Link

Comments

Post a Comment

Popular posts from this blog

Avoid Proxy for HttpClientRequest - IOB-090007 Network error (send(), errno=10054: an existing connection was forcibly closed by the remote host

This is Friday night 8:10 PM and I was frustratingly stuck with an annoying issue on something that I have done so many times, but still unable to figure out what is wrong since last night. Finally it was a silly mistake and I found that. So wanted to capture it so that I don't need to spend another day and half just to figure out why the same thing is not working I was making a call to Silverpop XMLAPI to get the jessionid via the login method. And the code is something like below, very basic one var http = new HttpClientRequest ( "http://api2.ibmmarketingcloud.com/XMLAPI" ); try { http . method = 'POST' ; http . header [ "ClientId_Internal" ] = "XYZABCD" ; http . header [ "ClientSecret_Internal" ] = "DSFDSOFNJSDF" ; http . header [ "Content-Type" ] = "application/x-www-form-urlencoded" ; var reqestBody = "xml=" + encodeURIComponent ( "<
Read more

Adobe Campaign: Call Java Script from Input Form

I came across a scenario where I need to do some custom auditing when some fields are  changed via an input form. So for that I had to call javascript functions from an input form. I have custom schema as cus:Preference with 1:1 join with nms:Recipient. And audit was required to capture who is making change to the preference page if any. Step 1: Create an entry in the input form for the soapCall.  <form>   <container > <!--Enter the form fields here-->   </container>   <leave> <!--servi = "name of the schema where the method is declared"-->     <soapCall name=" auditPreference " service=" cus:Preference ">       <param exprIn="[@id]" type="int"/>       <param exprIn="[@recipientId]" type="int"/>       <param exprIn="[@prefAllCommunications]" type="boolean"/>       <param exprIn="[@prefAllCommunicationsModifiedDat
Read more

Broadlog Resequencing in Adobe Campaign Classic

 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 is uni
Read more