publish a table as odata generates a error

[Markus]

Hi

I do have a Table with a ID Identity and a ParentID related to the ID (to provide a Treeview Data).

If i publish this as a odata service i get following error:

The ends of a ResourceAssociationSet cannot both have the same ResourceType and ResourceProperty values. If this is a self-referencing association, the ResourceAssociationSet must be unidirectional with the ResourceProperty on one of the ends set to null.


Any idea?

[Viktor Zhivkov]

Hi Markus,

The issue you are describing is a regression that we have found very recently and we are working to fix it.
You can expect the bug fix in the Q3 2012 Service Pack release, but unfortunately I cannot give you clear release date for it.

If you are pressed with your project schedule and have no time to wait before the fix is published, please let us know so we can create a temporary work around the issue.

Please excuse us for the inconvenience.

All the best,
Viktor Zhivkov
the Telerik team

[Markus]

Hi Victor,

Any update on this?  Get disturbing in my Project...

Regards
Markus

[Viktor Zhivkov]

Hi Markus,

The bug is fixed and you can expect the updated assemblies with the Q3 2012 Service Pack release in the last week of November or the first one of December.

Thank you for your patience.

Regards,
Viktor Zhivkov
the Telerik team

[John]

I'm having the same issue. I downloaded the version released 12/12 to see if that fixed the error, and I am still having it.  Did it make the release?  Thanks.

[Viktor Zhivkov]

Hi John,

In our test environment the original issue that Markus has reported cannot be reproduced any more.
I have been able to successfully expose NorthwindOA database (which is based on the original Northwind database with some additions) through Data Service and was able to create a service proxy using Add Service Reference in a Silverlight project.

Can you verify that you are referring to the latest available build of OpenAccess (Q3 2012 SP1 version 2012.3.1209)?
If you still can reproduce the issue, please send us the model with the associations that break the service metadata generation so we can analyze it and fix any remaining issues.

All the best,
Viktor Zhivkov
the Telerik team

[Allen]

I am experiencing the issue as well.  I am using the Northwind DB and getting the error when I try to use the Employees table because it has a self-referencing "manager" ID.  I had thought that maybe the navigation association name was a problem because when I auto-generated the table, it added an "Employees" navigation for the manager's subordinates.  Because of that, I renamed the navigation from "Employees" to "ManagedEmployees," but I still received the error.  However, when I deleted the association, the service worked just fine.  Hope that helps in finding the issue.

[Viktor Zhivkov]

Hi Allen,

We are still unable to reproduce the issue you have described.

In our test environment self-reference defined in the Employee entity works fine.
I can access the $metadata, ?wsdl and mex endpoints of the service and create service reference successfully in Silverlight 5 and Windows Forms applications.
I have tested both Data Services V2 and V5.0 in Visual Studio 2010 and 2012.

Can you define the steps that you do in order to reproduce the issue?

I have enabled the file upload for this thread and I would like to ask you for a reproduction project that includes the bin folders of the web application and has the model that triggers the issue.

We are looking forward to your feedback.

Greetings,
Viktor Zhivkov
the Telerik team