Error -xtk-170030 empty value is not valid as a key for element srcSchema of document type Source schema of entities (xtk:srcShema) while editing any schema

[alwaysDigital]

Dear All,

I am getting error while editing any schema or creating new schema in sandbox environment. I see one of our out of box schema(nms:seedMember) got corrupted and when I try to regenerate the same, getting xtk/170030 error so basically this error is not allowing me to do any modification in any of the schema. Kindly help me if you have encountered similar issue.

Attaching screenshot of error for your reference.

[alwaysDigital]

Server Details>

[ds_merkle]

This advice led me down the wrong path. For the xtk-170030 error, after trying all the steps above, we found out that it was simply a naming issue in my data schema import wizard. The NAME of a table/view must contain underscores i.e. TEST_TABLE versus TEST TABLE.

[Adhiyan · Accepted solution]

Hello ,

There is one schema in your system which does not have the correct definition or missing values in the <srcSchema tag.

Check for schemas by last modified and see which schemas were created just before you started to have the issue. Then check which schema does not have a correct definition of the srcSchema tag. That is causing issues.

When you create a new schema , all schemas are regenerated to generate new links which can be created by the new schema and hence it does allow to create anything if even one schema is logically wrong.

Regards,
Adhiyan

[ds_merkle]

This advice led me down the wrong path. For the xtk-170030 error, after trying all the steps above, we found out that it was simply a naming issue in my data schema import wizard. The NAME of a table/view must contain underscores i.e. TEST_TABLE versus TEST TABLE.

[alwaysDigital]

Hi Adhiyan,

Thanks for your response. I checked all schema with last modified field. I found some custom schema which showed date near to date when I saw issue. So cleaned up all but still issues remains same.

I have asked Adobe support to restore nms:seedMember once and see how it goes.

Let me know if you find any other approach to dig in and fix this. Thanks a lot.

[alwaysDigital]

Hi Adhiyan,

We have found the issues and yes it was related to incorrect schema configuration. Thanks a lot!

Cheers,

Always Digital.