Squidex CLI Backup not backing up SchemaIds

atfdynamo5 · March 8, 2022, 2:38pm

I have…

[ x ] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.

I’m submitting a…

[ ] Regression (a behavior that stopped working in a new release)
[ x ] Bug report
[ ] Performance issue
[ ] Documentation issue or request

Current behavior

“schemaIds”: [
“policy-category”
]

Expected behavior

“schemaIds”: [
“”
]

Minimal reproduction of the problem

When using Squidex CLI to export schemas using:
…/sq sync out -t schemas ./
…the parts where the schemaids should be are replaced by the referenced schema’s name rather than its guid.

Environment

App Name: squidex

[ x ] Self hosted with docker
[ ] Self hosted with IIS
[ ] Self hosted with other version
[ ] Cloud version

Version: [VERSION]

Browser:

[ ] Chrome (desktop)
[ ] Chrome (Android)
[ ] Chrome (iOS)
[ ] Firefox
[ ] Safari (desktop)
[ ] Safari (iOS)
[ ] IE
[ ] Edge

Others:

Sebastian · March 8, 2022, 6:44pm

Hi,

this is intended. The schema ids are not useful because after a “sync in” they are different. Therefore the sync in does everything in 2 steps:

Create all schemas without any setup to get a mapping from schema-name to schema-id.
Update all schemas and resolve the final schema ids with the result from the previous step.