Custom Primary Key

Hi,

This is achievable by adding several additional lines of code into your xml schema.

Firstly, you need to advise the schema that that primary key will not be auto generated.

If you look at an out of the box schema (such as nms:recipient) you will notice this line of xml:

<element autopk="true"

In order to use your own primary key, you can add:

<element autopk="false"

So for example in my custom schema that I can create with my own primary key being generated: my line of code would look like this:

<element autopk="false" label="PK Demo" name="pkDemo">

Then, I just need to tell the schema which attribute would now become the primary key. So this is the attribute that i will use as my PK:

   <attribute label="This is my Primary Key" name="id" type="long"/>

So i add the following xml :

    <key internal="true" name="id">

      <keyfield xpath="@id"/>

    </key>

This should now result in the following:

If you need any further assistance let me know.

Dan Lewis

Tech Marketer Solutions

http://www.techmarketersolutions.com

Hi,

I test your approatch and it creates a UNIQE INDEX in the SQL Server but I need it to be a PRIMARY KEY on the database server as well.

Can you please share your schema xml?

<element label="Black List Pure Email Test" name="blackListPureEmailTest">
  <key internal="true" name="id">
      <keyfield xpath="@email"/>
      <keyfield xpath="@brand"/>
    </key>
    <attribute label="Brand" length="50" name="brand" type="string"/>
    <attribute label="Country" length="2" name="country" type="string"/>
    <attribute label="Email" length="128" name="email" type="string"/>
    <attribute label="No longer pure email" length="128" name="blackListPureEmail"
               type="boolean"/>
    <attribute label="Created date" name="created" type="datetime"/>
  </element>

And the SQL generated:

CREATE TABLE ElsBlackListPureEmailTest(
  iBlackListPureEmail tinyint NOT NULL Default 0, 
  sBrand nvarchar(50), 
  sCountry nvarchar(2), 
  sEmail nvarchar(128), 
  tsCreated datetimeoffset(6)
);
CREATE UNIQUE INDEX ElsBlackListPureEmailTest_id ON ElsBlackListPureEmail
Test(sEmail, sBrand);

Hi,

Your code looks correct to me. I have tested and works. On the database layer; OOTB schemas have the same pattern. In adobe campaign here is am example of the Tracking Logs schema where TrackingLogId is the pkey in the schema:

You can see it has a red key next to it to indicate primary key.

Whereas if I look in the underlying database - it see this:

So what you are experiencing is by design.

I hope that helps clear that up.

Kind Regards,

Dan Lewis

Tech Marketer Solutions

http://www.techmarketersolutions.com