Closed karlcz closed 4 years ago
The Reference.update
API in ermrestjs was using the wrong Reference.location.schemaName
value which might be null. I changed it to use the correct Reference.table.schema.name
instead. The edit should now work properly. The other parts of ermrestjs are using the correct API, so there wasn't any need for further changes.
@karlcz can you please try this again and verify the fix?
If you go to a recordedit URL without an explicit schema name, the app mostly functions except for multi-record edit submission.
An error banner is displayed
Schema null does not exist
. Doing the same flow for a single-record edit will succeed, so it seems to be multi-record specific code...I wonder if the application should just normalize the URL during startup, finding the implicit schema and adding the missing schema name qualifier to the location bar and other app state?