Forum Discussion
Schedule refresh failed: We cannot convert the value "[Record]" to type Record
Hi,
I have a Power BI Desktop file, to which I connected my Dynamics 365 organization through OData. The file is published into an online dashboard.
Few days ago, I started receiving the following error whenever the dataset automatically refreshed: We cannot convert the value "[Record]" to type Record. Also, in one of my tables from Power BI Desktop, I'm getting the following error:
DataSource.Error: OData: The context URL 'https://[OrganizationURL]/api/data/v8.2/$metadata#owners/$entity' is invalid.
Details:
DataSourceKind=OData
DataSourcePath=https://[OrganizationURL]/api/data/v8.2/opportunities([OpportunityID])/ownerid
However, the desktop file can be published manually, but strangely, it doesn't appear in the Refresh history of the dataset whenever it's published likewise.
I did perform few changes lately, but it would take forever to explain all of them, that's why I would need a bit of your guidance here.
I would like to know if anybody encountered this before, and it would be nice if anybody could guide me a bit, why this can happen and what the resolutions would be.
Also, if there's need of more info, I'll be more than happy to provide.
Thank you,
Tibi
2 Replies
TiberiuNicolae I'm not very well versed on M/Power Query yet but I do know that some changes can really muck up your file. Here was a great blog I read by Gil Raviv, I don't know if your scenario fits any of the pitfalls, but I would look in the actual M code to determine if one of your changes didn't make it's way out of the data pull and there is still a reference to something that no longer exists.
Hi TiberiuNicolae,
Do you have fastcombine turned on on the personal gateway? If not here's a link on how to do it:
https://powerbi.microsoft.com/en-us/documentation/powerbi-refresh-enable-fast-combine/#turn-on-fast-combineHere is a similar thread in which a workaround was mentioned. Could you go to check if works in your scenario? :smileyhappy:
Regards
