- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi David,
you are right. Your solution works on fresh installation of Adobe Campaign (checked on VM).
Well, my problem persist on my prod instance, because there is another additional element (below) with the same name in default seedMember schema. I think this stops your solution to work properly.
This additional element is located after first element (below) with defined templates (I have used your screenshoot, ignore green line)
How can I bypass this element with the same name as element which is already bypassed?
Regards,
Milan
Views
Replies
0 Likes
Total Likes