How to safely remove Target Mapping schemas?

Avatar

Avatar
Give Back 5
Level 3
marcinkacz
Level 3

Likes

19 likes

Total Posts

46 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 10
View profile

Avatar
Give Back 5
Level 3
marcinkacz
Level 3

Likes

19 likes

Total Posts

46 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 10
View profile
marcinkacz
Level 3

29-09-2017

Hi Community Members,

Lately I was working on non-standard recipient table (External recipient table) and Target Mapping for it in our dev environment. I finished my work and I want to remove all components: form, folders and schemas.

Unfortunately, I know that removing Tracking logs (My_custom_schema_name) schema from set of Target Mapping schemas (this set contains also dedicated Delivery Logs and Exclusion Logs schemas) will raise error in one of default technical workflow - in Tracking workflow. It will return error like this:

The file '/usr/local/(...)/schema/trackingLog_MySuffix.xml' does not exist on the server. Unable to load the document of identifier 'cus:trackingLog_MySuffix' and type 'xtk:schema'.

Do you know how to safely remove all 4 schemas (main describing external recipient table and 3 Target Mapping-related)? I want to be sure that Tracking technical workflow won't search for trackingLog_MySuffix.xml.

Thank you,

Marcin

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile

Avatar
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile
florentlb
Level 10

10-10-2017

Hi Marcin,

Creating a new target mapping is like modifying the database, as it creates new tables that are interconnected with each other. Hence this is not recommended to do so. This is like removing a package, which is not possible in Adobe Campaign for data base integrity reasons.

What we usually recommend if that is absolutely necessary to remove it is to create a fresh instance.

Hope this helps,

Florent

Answers (0)