cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Regular Visitor

Getting DataSource.NotFound: OData: Request failed (404) in Excel Power BI

I have an Odata V4 service written with java olingo.

When I try navigating between entities in Excel Power BI I get this error:

 

DataSource.NotFound: OData: Request failed (404): The remote server returned an error: (404) Not Found. (Resource not found.)
Details:
DataSourceKind=OData
DataSourcePath=http://localhost:8080/odata/v4/shared_spaces/1001/workspaces/1002/features('1011')/product_areas('1034')/tests('1016')/owner
Url=http://localhost:8080/odata/v4/shared_spaces/1001/workspaces/1002/features('1011')/product_areas('1034')/tests('1016')/owner

 

The problem is that for some reason Power BI builds the URI with the the entity set name instead of the property name in the entity. What I mean is that the entity product_areas has a property called test. If the URI was:

http://localhost:8080/odata/v4/shared_spaces/1001/workspaces/1002/features('1011')/product_areas('1034')/test('1016')/owner

the URI would've worked.

But excel builds the URI with tests (like this: http://localhost:8080/odata/v4/shared_spaces/1001/workspaces/1002/features('1011')/product_areas('1034')/tests('1016')/owner).

Any idea what am I doing wrong here?

Thanks,

Adi

5 REPLIES 5
Community Support
Community Support

@AdiIsen,

 

This issue is more related to Odata URI, you may check if the Odata URI is valid. In addtion, if this issue still persists, I would suggest you to use built-in connector or content pack/app instead to connect to the data source.

 

Community Support Team _ Jimmy Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

@v-yuta-msft

It looks like Excel (2013 + Power Query plugin) generated the invalid URI:

http://localhost:8080/odata/v4/shared_spaces/1001/workspaces/1002/features('1011')/product_areas('1034')/tests('1016')/owner

 

I was expected from Excel to generate the following:

http://localhost:8080/odata/v4/shared_spaces/1001/workspaces/1002/features('1011')/product_areas('1034')/test('1016')/owner

 

The question is why Excel is using the the entity set name (tests) instead of the navigation property name (test) as it should be?

 

below you can find our metadata (the relevant lines are marked in purple).

 

<EntityType Name="product_area">
<Key>
<PropertyRef Name="id"/>
</Key>
<Property Name="creation_time" Type="Edm.DateTimeOffset"/>
<Property Name="client_lock_stamp" Type="Edm.Int64"/>
<Property Name="has_children" Type="Edm.Boolean"/>
<Property Name="version_stamp" Type="Edm.Int64"/>
<Property Name="description" Type="Edm.String"/>
<Property Name="name" Type="Edm.String"/>
<Property Name="id" Type="Edm.String"/>
<Property Name="last_modified" Type="Edm.DateTimeOffset"/>
<NavigationProperty Name="parent" Type="OData.Octane.product_area" Nullable="false"/>
<NavigationProperty Name="test" Type="Collection(OData.Octane.test)"/>
<NavigationProperty Name="children" Type="Collection(OData.Octane.product_area)"/>
<NavigationProperty Name="work_item" Type="Collection(OData.Octane.work_item)"/>
</EntityType>

<EntitySet Name="tests" EntityType="OData.Octane.test"/>

BTW, what do you mean by built-in connector? I'm using Excel Power Query plug in.

 

Thanks,

Adi

@AdiIsen 

 

Did you end up resolving this issue? I am having a similiar problem...

 

Thanks in advanced

No, I still don't have a solution for this

@AdiIsen,

 

It seems this issue is caused by the power query plugin in excel. I would suggest you to post this issue to excel forum for further help.

 

Community Support Team _ Jimmy Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
secondImage

Happy New Year from Power BI

This is a must watch for a message from Power BI!

December Update

Check it Out!

Click here to read more about the December 2020 Updates!

Community Blog

Check it Out!

Click here to read the latest blog and learn more about contributing to the Power BI blog!

Get Ready for Power BI Dev Camp

Get Ready for Power BI Dev Camp

Mark your calendars and join us for our next Power BI Dev Camp!.

Top Solution Authors
Top Kudoed Authors