Skip to content

GH Issue 1779: Load external schemas on data sources with a display name - #8265

Closed
labkey-adam wants to merge 2 commits into
developfrom
fb_external_schema_display_name_1779
Closed

labkey-adam wants to merge 2 commits into
developfrom
fb_external_schema_display_name_1779

Conversation

@labkey-adam

Copy link
Copy Markdown
Contributor

Rationale

External schemas on a data source with a configured display name failed to load, because schema metadata loading resolved the display-name-qualified schema name back to a data source by name. Fixes GH Issue 1779.

Related Pull Requests

  • None

Changes

  • Schema metadata loading takes the schema name from the scope it already has instead of looking the data source up again by its display name.

@labkey-adam

Copy link
Copy Markdown
Contributor Author

Superseded by #8272, which targets release26.11-SNAPSHOT; the fix reaches develop via the release merge-forward.

@labkey-adam labkey-adam closed this Nov 2, 2026
@labkey-adam
labkey-adam deleted the fb_external_schema_display_name_1779 branch November 2, 2026 18:57
labkey-adam added a commit that referenced this pull request Nov 2, 2026
…ame (#8272)

## Rationale
External schemas on a data source with a configured display name failed
to load, because schema metadata loading resolved the
display-name-qualified schema name back to a data source by name. Fixes
[GH Issue 1779](LabKey/internal-issues#1779).

## Related Pull Requests
- Replaces #8265, which targeted develop

## Changes
- Schema metadata loading takes the schema name from the scope it
already has instead of looking the data source up again by its display
name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant