We have encountered an issue in ACS while creating a new schema.
We created a new schema which was joined with profile extension schema based on custom columns (email and name).
When defining links, we have to give a link id which says it should contain maximum 30 characters. It do not mention anywhere which characters are allowed or not. So we used hyphen in that name and it was accepted by UI (for ex linkschema1-abc).
Now when we prepared the publication we received no error and publication went successfully.
However, after it, the profile schema went missing from instance and all related schemas started throwing error.
When we did diagnosis, it showed error in publication logs that 'XTK-170036 Unable to parse expression "linkschema1-abc"'.
We tried everything like deleting schema/link, redraft schema, repaid DB option but nothing worked because last publication was successful and new publications will throw error due to invalid definition of profile schema.
We contacted support and support suggested they cannot fix the schema and DB would need to be restored.
Now my concerns and questions are:
If there was an issue with link name or something else, why did the ACS publication went successful. It should have went to error.
If the issue is related to '-' in link id, why it is accepted as character in UI input field.
There is no option in product for us to restore it back to an old successful publication. (This option is available only when last publication went in error)
Repair DB option while preparing publication does nothing in this scenario.
In Diagnosis>Data Schemas we can only see XML structure but cannot edit it. If this was available, we could have fixed the issue. And looks like this is not even editable by Adobe tech team. This really needs to be editable as else whats the point of having it.
If above are actual behaviors of product then these should be fixed in ACS.
If these are resolvable, then I would like to know how it could be fixed by our self and if some else has encountered this issue before. Would appreciate any help on this.
I would recommend opening up a ticket with Campaign Support. Based on what you are saying, it sounds like either a potential bug with us not accepting the hyphen, or the need for guardrails to be added to the product to prevent invalid characters from being added.
Additionally, we may need to enlist the services of Adobe Campaign Ops to update the table from the back-end if indeed the hyphen is the problem.