Yes it does. The non-gsExt one is a Delivery Logs data schema created
when target mapping was done on a new table. Is it recommended that I
just modify that one since it isn't a core data schema instead of
creating an extension and modifying the extension?We had an Adobe
architect create custom target mapping and Delivery Logs for us last
year and I was following similar steps.Thanks again for your answers.
Thanks Vipul. Based on the instructions on this user doc I used a
different namespace to extend a schema I created. I used a different
namespace but same
attached a couple of screenshots. The second one (starting with gsExt)
is the extension which is giving the error. Do we have to use a
different value for extendedSchema even if it has a different
Hi Vipul,I'm getting the same error with the circular dependency but I'm
not sure how to avoid this. I used the wizard to extend the schema to
create the schema extension, so wondering whether it is sufficient to
just change the value for extendedSchema.