It always show us error "Circular dependency on schama extension 'cus:address'" when we w ere saving an editing schema.Whether you choose 'Create a table in the data template' or ' Extend the data in the table using an extension schema', it will prompt such a mistake :
Thanks very much. As you said, we did find the cause of the error in the schema cus: address。
The snapshot of cus:address:
Glad to know that this has been resolved.
For other readers, the name of schema extension was cus:address and the schema it was trying to extend was also cus:address, thus causing the circular dependency. Schema being extended is maintained in attribute extendedSchema of root node.
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.
I've 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 namespace?
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.