Errors when importing schema within UI

I have…

  • Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
  • Used code blocks with ``` to format my code examples like JSON or logs properly.

I’m submitting a…

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

Current behavior

When importing a schema (using json) with values in the "“fieldsInLists” array, an error appears within a red banner like so:

Expected behavior

create the schema without error. At times, the error will throw, yet the schema will still be created.

Minimal reproduction of the problem

  1. Click on Create new schema
  2. Type the name of your new schema
  3. Click Import button at the bottom of the dialog
  4. Paste your Json of a schema from some other Squidex instance
  5. Click Create

Environment

App Name:
schema-bug-report-example

  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: [7.0.0.0]

Browser:

  • Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge

Others:

The issue is extremely similar, if not identical to this one (so much so, the steps to reproduce are identical):

My assumption is that the old format for field names is used, which is not made backwards compatbile on this screen. Can you provide an example json?

Do you mind providing a link to the new format please, or perhaps briefly describe it if such a resource doesnt exist? thank you Sebastian!

The old format was this

<data-field>
meta.id
meta.lastModified

This has been changed to

data.<data-field>
id
lastModified

To be consistent with the JSON structures.

thank you! Below is the content of the fieldsInList field.

    "fieldsInLists": [
        "data.id",
        "data.someField",
        "data.name",
        "status.color"
    ],

perhaps data.id is causing the issue? If thats the case, how do we go about fixing it?

Are you sure that you are on 7.0.0.0? I think the UI does not show the minor versions. Your docker tag is more relevant. And your broken JSON would help, because I do not have issues with data.id

Im not sure what you mean by docker tag? we have not had to setup docker containers as we are using the cloud version. I cant post our full json, however I will reproduce the error in a test app that doesnt include company IP and will get back to you. We are busy right now, so it might take a couple of days.

Thank you for all the help you provided Sebastian! I’ll return with an example shortly.

1 Like