Finance | Project Operations, Human Resources, ...

OData Integration: string does not contain definition for EntityTracker

(0) Share

Report

Posted on by mateenahmed

Hi,

I am trying to implement Odata Integration with the help of the following article:

http://shootax.blogspot.com/2019/10/d365fo-data-integration-by-odata-part-1.html

But when I try to build the Utility Project, the following error shows up:

Can someone please guide as to what changes I should make to make this work?

I only changes the following line in the Utility Class:

public const string MetadataDocumentUri = https://usnconeboxax1aos.cloud.onebox.dynamics.com/data/$metadata/;

Help would be highly appreciated. Regards.

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Kevin Xia Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

Judging from the error message, maybe the first parameter of this method EntityTracker should not be of string type, but you defined MetadataDocumentUri as string type and passed the parameter, so the system will have this error, the parameter type that the system wants to get is Microsoft.OData.Client.DataServiceContext instead of string.

Best regards,

Kevin

Was this reply helpful? Yes No
Martin Dráb 238,782 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Your code shouldn't even compile. You seemed to mean this instead:
public const string MetadataDocumentUri = "https://usnconeboxax1aos.cloud.onebox.dynamics.com/data/$metadata";

Was this reply helpful? Yes No
Arif Hussain 214 on at

Like (0)

Report
Copy link

Link copied!

Hi mateenahmed,

Did you find any solution to this problem as I am also getting the same issue while creating and building the OData connected services?

Was this reply helpful? Yes No
Suggested answer

Arif Hussain 214 on at

Like (0)

Report
Copy link

Link copied!

Hi mateenahmed,

I was getting the same issue that you shared and the reason is due to creating a console application and then configuring OData Connected Service. I solved it by first creating a class project not console application then configured OData Connected Service. Plus, when I added the service address and press next, the list of entities was displayed and I selected just one of that entities.

Note: You can still access all entities in the code.

I did these two steps and it worked really fine for me. I recently consumed OData data entities using OData connected service in .Net Console Application and it really worked for me.

Hope it will help for you too. If not, please let me know.

Was this reply helpful? Yes No
Veeraraj 22 on at

Like (0)

Report
Copy link

Link copied!

I have the same issue as well, Could you guys managed to fix this issue. Please suggest.

Was this reply helpful? Yes No