Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OData: Reinstate NavigationProperties #82

Closed
issa-tseng opened this issue Apr 6, 2018 · 1 comment
Closed

OData: Reinstate NavigationProperties #82

issa-tseng opened this issue Apr 6, 2018 · 1 comment
Assignees
Labels
enhancement New feature or behavior
Milestone

Comments

@issa-tseng
Copy link
Member

Currently, we do not formally express the relationships between tables in OData, largely because Power BI currently considers any NavigationProperty within a ComplexType invalid, and will reject the metadata document. This is equivalent to a repeat within a group in our parlance—an exceedingly common case.

Per the OData 4.0 spec, this construction should absolutely be valid, and it looks like Power BI simply hasn't caught up to the spec here (perhaps because the ADO.NET EF has yet to catch up either). Once it does work, we should ideally restore the link, in addition to a ReferentialConstraint describing the navigation relationship (the join).

issa-tseng added a commit that referenced this issue Apr 6, 2018
@issa-tseng issa-tseng changed the title Reinstate OData NavigationProperties OData: Reinstate NavigationProperties Apr 6, 2018
@issa-tseng issa-tseng added the enhancement New feature or behavior label Jun 22, 2018
@issa-tseng
Copy link
Member Author

so, it looks like now this construction no longer fails out immediately in pbi (good) but it doesn't really do what i'd expect. needs more work.

@issa-tseng issa-tseng added this to the v0.7 milestone Aug 1, 2019
@issa-tseng issa-tseng self-assigned this Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or behavior
Projects
None yet
Development

No branches or pull requests

2 participants