When importing a jCatalog (JSON database catalog), only the first catalog and first schema in the file are read; any additional catalogs or schemas are silently ignored. Update the import so all catalogs and all schemas are read and their tables, columns and relationships are imported completely.

This becomes relevant because the new Excel-to-jCatalog conversion wizard can now produce catalogs that contain more than one schema or catalog (for example when the schema is given by a separate column, or as a prefix in the table name such as dbo.Customer or module$entity). Today those extra schemas would not appear after import.

Single-catalog/single-schema files continue to work exactly as before.