This question is locked. New answers and comments are not allowed.
So I have Oracle in the backend and an OpenAccess ORM generated with a View in it. The View in the database does NOT have a PK constraint but the main underlying table does and Oracle will not let me add a PK to the view because it recognizes the PK from the underlying table and tells me that I can only have one PK. According to the OpenAccess documentation........
"By default, if your view doesn't have a primary key, the corresponding entry in the Add OpenAccess Service wizard is disabled. If you want to expose a view through a service, you need to specify a primary key in the Visual Designer."
So I did this. The Visual Designer shows the little key signifying that the column is a PK. But I sill cannot add the View to the entity collection when trying to create an oData v3 service. I click and click and click on the little checkbox to add it to no avail. I tried clearing Visual Studio cache. I tried rebuilding the solution. I tried I tried clicking harder. I tried crossing my arms and wiggling my nose. I tried a little voodoo magic. Apparently my kung fu is weak today.
Please advise.
"By default, if your view doesn't have a primary key, the corresponding entry in the Add OpenAccess Service wizard is disabled. If you want to expose a view through a service, you need to specify a primary key in the Visual Designer."
So I did this. The Visual Designer shows the little key signifying that the column is a PK. But I sill cannot add the View to the entity collection when trying to create an oData v3 service. I click and click and click on the little checkbox to add it to no avail. I tried clearing Visual Studio cache. I tried rebuilding the solution. I tried I tried clicking harder. I tried crossing my arms and wiggling my nose. I tried a little voodoo magic. Apparently my kung fu is weak today.
Please advise.