Adobe Campaign Standard

tumuzhuanjia · 2:09:04 AM

Hi :

I create a new schema and updated database . and I meet the follow problems:

(1) When I write a record by the inner form, the Client console tell me the follow error happend.

But my attribute is quite simple and I did not define a key atttribute.

Would you like to tech me how to resovle it?

---------------------------
Adobe Campaign - Client console
---------------------------
Key values missing (document of type 'bfwechat:wechatFan', from path 'wechatFan').
XSV-350023 Unable to save document of type 'bfwechat:wechatFan'.
---------------------------

My Schema:

(2) When I delete a schema and update database structure, I can't find the schema name to drop it.

How can I do that?

Best regards.

Vipul_Raghav · 2:41:21 AM

Hi,

(1) You have not defined a primary key column for your schema. You can either define it explicitly or use the automated column generated via autopk="true"

Please refer to link https://docs.campaign.adobe.com/doc/AC6.1/en/CFG_Schema_Reference_Elements_and_attributes.html

(2) The campaign allows you to delete a schema but it will not delete the underlying table. If you wish to delete it, fire the SQL directly from backend, or use the SQL code activity in a workflow (Be cautious not to delete something else)

Regards,

Vipul

원본 게시물의 솔루션 보기

Vipul_Raghav · 2:39:43 AM

Hi,

(1) You have not defined a primary key column for your schema. You can either define it explicitly or use the automated column generated via autopk="true"

Please refer to link https://docs.campaign.adobe.com/doc/AC6.1/en/CFG_Schema_Reference_Elements_and_attributes.html

(2) The campaign allows you to delete a schema but it will not delete the underlying table. If you wish to delete it, fire the SQL directly from backend, or use the SQL code activity in a workflow (Be cautious not to delete something else)

Regards,

Vipul

Vipul_Raghav · 2:41:21 AM

Hi,

(1) You have not defined a primary key column for your schema. You can either define it explicitly or use the automated column generated via autopk="true"

Please refer to link https://docs.campaign.adobe.com/doc/AC6.1/en/CFG_Schema_Reference_Elements_and_attributes.html

(2) The campaign allows you to delete a schema but it will not delete the underlying table. If you wish to delete it, fire the SQL directly from backend, or use the SQL code activity in a workflow (Be cautious not to delete something else)

Regards,

Vipul

tumuzhuanjia · 2:55:33 AM

Hi Vipul:

Thank you. It is helpful to me.

blair_elzinga · 8:36:19 AM

A note on the physical delete of the table - if your solution is hosted by Adobe and not on-premise, then you don't have access to the database to delete the table. You'll need to open a ticket with support to delete the table. They will in turn open an internal ticket with tech-ops to do the actual delete. Quite a pain to get things deleted for hosted customers!

Vipul_Raghav · 10:21:47 PM

Hi Blair,

Thank you for highlighting an important point.

It is indeed a little difficult to get the physical table deleted when the intent is actually to delete it.

The reason for not building the physical delete of SQL table at the delete of schema is because we usually see one case per week where a user deleted the schema by mistake. In such scenario, just importing it from another environment helps him recover the data back again.

If the feature was developed the way you @tumuzhuanjia wanted it to be, we would have to restore last days backup on the current database.

However, based on customer's feedback we do have an Enhancement Request in the pipeline for this feature.

Hopefully, we will have a special feature in one of the future builds. As of now, the current build 8797 doesn't have it.

Regards,

Vipul

blair_elzinga · 12:59:01 PM

I think the client U/I is used by folks that aren't savvy with databases, so I understand you point there. However, there isn't any good reason why you couldn't expose database functions like delete table to the data API, which isn't used by folks who accidentally delete tables.

Glad to hear that you're thinking about addressing this in some way. Look forward to it. Thanks.