My main goal was to have "codinterno" as a unique field.@ParthaSarathy  suggested doing: <dbindex name="myIndex" unique="true"><keyfield xpath="@myField"/></dbindex>Since it was my main goal to have that as a unique field, Paratha suggestion works for my case.Thank you both.

Since Recipients table already has a PK, I cannot make my field a PK so it is unique.So I cannot use:autopk (boolean): if this option is activated (autopk=“true”), a unique key will be automatically defined. This option may only be used on the main element of the schema. Warning, Adobe Campaign only...

I'm adding some fields to the abc:recipients (recipient's extension) schema. It currently has 01 PK in the base recipient schema. I need to add an attribute from the extension also as PK.  So both are not a combined PK, rather individual PKs.Is this ok? This is how I have set the codinterno field as...

Hi @_Manoj_Kumar_  any documentation that backs this up?Mostly the new Push formats.  Adobe team confirmed to me that SDK update is not requeried, but didn't know if the new formtas you mentioned would be available upon upgrade of it.Thank you.

We're moving to V8. We already have Adobe Campaign 7 on our Mobile App to send Push Notifications....  Do we need to update the SDK on our app?We have assigned an Adobe Team for this, but they don't know... they will invistigate. So I wanted to ask here, in case someone has experience with this.

Hi, those are differente... that one was about 1-1 relationship... this one is a 1-N relationship

I ended up with: So in abc:agents you add an element inside the main element of the schema (you don't need to modify recipients schema. revLink, revLabel and revTarget create the link in recipients for you):<element integrity="normal" label="Recipient" name="recipient" noDbIndex="true"revCardinality...

I've a schema abc:multipleops (that stores all operations - transactions - related to a recipient) that I need to stablish a N-1 relationship with Recipients. The relationship should be visible from both sides.documentation says, I just should not type: revCardinalityrevCardinality (optional): with ...

It is not clear if point onw should go on acb_agents or recipients... because in point 2 you mentioned "You will only need to modify the recipients schema ..." so with this you can imagine point 1 goes inside acb_agents.... whoever... point 1 has: target="abc:agents"And you shouldn't target the same...

I've found other thread with the same question, but answer was not clear enough for me. I need to link "nms:recipients" (or our extended abc:recipients table) and abc:agents.  Both have the column codinterno. It is a PK in both schemas.So in my abc:recipients (extension schema), accorind to docs, I ...