Adobe Campaign v8 - Database Structure Update - Not Updating Schema Structure

[NataliR]

Hello!

Hoping someone can help. 

When I run the Database Update Wizard none of the schemas that I have created or have made updates to are being updated. The update script shows me every schema I've built with the "Synchronize" checkbox checked, but the SQL script shows every line of code commented out (see screenshot). 

I noticed this occurred after I created an extension of the nms:recipients schema using the "cus" namespace, but then created a new extension of the nms:recipients schema using a different namespace (let's call the new namespace "xyz"). I subsequently deleted the extension with the "cus" namespace thinking the database structure update was affected due to having two extensions of the nms:recipients schema with different namespaces.

Summary of Steps Taken:

1. Created "cus" extension of nms:recipients schema

2. Added attributes to cus:recipients schema and updated the database structure successfully. (Verified new attributes were showing as part of the structure)

3. Created "xyz" extension of nms:recipients schema and copied over the working xml from cus:recipients for the attributes I needed in xyz:recipients

4. Updated the database structure. Result: No update

5. Deleted cus:recipients schema and updated the database structure. Result: cus:recipients no longer existed as a schema, but xyz:recipients was still not showing up in the schema structure, nor was it triggering an update in the Database Update Wizard.

Thank you!

Natali

[_Manoj_Kumar_]

Hello @NataliR 

Extend the schema only once and add the new columns/attributes to the same extended schema. Don't create another extension of same schema

[NataliR]

Hi @_Manoj_Kumar_, thank you for your response.

I had to update the namespace for the client (xyz company), so unfortunately the schema has already been extended twice.

I'm hoping someone else has encountered this issue and has found a solution/workaround.

Thank you,

Natali

[Denis_Bozonnet]

Hi @NataliR 

What you observed is normal, the Upgrade database process is detected new / removed elements by comparing the table in the database with the whole nms:recipient entity, since you've got the columns already defined via the cus extension, defining the same columns in a different extension won't change the table structure in the database: hence it does not detect any changes on the table structure,

You can see the table structure in the Documentation tab of Data Schema, you will find out the columns added via the cus namespace entity...

So what you see is normal, nothing wrong here...the namespace doe snot intervene in the table structure

Thanks

Denis.

[NataliR]

Hi @Denis_Bozonnet, thank you for your response. 

My explanation may not be completely clear.

What I’m saying is that none of the fields appear in the structure. Not from cus:recipients or xyz:recipients. Not only is the recipients schema not being updated, but none of the new schemas (not extensions) are being updated with the wizard.

Thank you!

Natali

[Denis_Bozonnet]

Hi @NataliR 

 Do you mean the fields from the 2nd extension aren't shown in Preview and in the Documentation tabs of the nms:recipient data schema itself? Normally in the Preview tab of the nms:recipient, you should see the fields from your 2nd extension...

In your new recipient extension, if you remove ALL elements, keeping the extension as an empty shelf, and if you do a Update database structure, what do you have?

Thanks

Denis.

[NataliR]

Hi @Denis_Bozonnet,

The fields from the 2nd extension schema are showing in the Preview tab but are not showing in the Documentation tab of the nms:recipient schema.

I tried your suggestion:

"In your new recipient extension, if you remove ALL elements, keeping the extension as an empty shelf, and if you do a Update database structure, what do you have?" 

Result: After removing all elements and saving my changes, I tried to update the database structure but there were no changes/updates detected for the recipients schema.

Let me know if you have any more ideas. This is very helpful! 

Thanks,

Natali