Current state OData instance being preserved upon refresh?

[iDataDrew]

I'm working with current state project data from an OData feed.  So there should only be one row per project.  However, after refreshing the data several times over a few weeks, some projects have multiple rows and some of the values are different in certain fields (e.g. baseline cost, baseline duration).  In order to troubleshoot this, I opened a new .pbix and imported the OData.  As far as I can tell, there's only one row per project, as it should be.  So, I'm wondering if some data has somehow been retained during refreshes, thus producing multiple rows for some projects?  Has anyone else run into this problem or one like it?

Thank you.

[v-shex-msft]

Hi @iDataDrew,

Have you checked on your source data? If your source contains same date records or duplicate records, it will return multiple rows.

In addition, if odata url conversion not work, you can also add current date filter in power query.

Regards,

Xiaoxin Sheng

[iDataDrew]

@v-shex-msft, thanks for the response.  I've been told that the source data is only showing one row for each project.  Could you explain further what you have in mind with the OData url conversion?  The data contains dates in it, such as start date, end date, baseline dates, etc., but it doesn't contain an actual date field, like today's date.

[v-shex-msft]

Hi @iDataDrew,

>>Could you explain further what you have in mind with the OData url conversion? 

It is a typo, in fact, I mean 'url conventions'.

For url conventions, you can check at below link:

URL Conventions (OData Version 3.0)

Regards,
Xiaoxin Sheng