Databases
StackOverflow2013
Postsdbo
POBreeze returns navigation properties in the metadata, but not on the entities
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBreeze returns navigation properties in the metadata, but not on the entities
    primarykey
    data
    text
    <p><strong>This question has been completely edited to actually outline the root issue after further investigation.</strong></p> <p>I was having trouble with no navigation properties appearing on my client side metadata. With deeper inspection of the breeze client side code, I've worked out that the following code in <code>parseCsdlNavProperty</code> (line 6181) is causing <strong>all</strong> my collection navigation properties to be ignored:</p> <pre><code>var constraint = association.referentialConstraint; if (!constraint) { // TODO: Revisit this later - right now we just ignore many-many and assocs with missing constraints. return; // Think about adding this back later. //if (association.end[0].multiplicity == "*" &amp;&amp; association.end[1].multiplicity == "*") { // // many to many relation // ??? //} else { // throw new Error("Foreign Key Associations must be turned on for this model"); //} } </code></pre> <p>The property referentialConstraint is undefined, and this causes breeze to ignore my related entites. Problem is I'm not sure a) why this is null, b) what this does, c) why breeze seems to hate this, when entity framework seems to be mapping things fine, d) how to fix it.</p> <p>So I've removed my entire metadata and examples of my model because it's just too much information. If there is information required, just let me know and I'll add it.</p> <p>Hopefully this makes the question a little more specific and easier to decipher.</p> <p>Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAdam
    1. USAdam
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBreeze returns navigation properties in the metadata, but not on the entities
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI can't tell from your post if your are having a problem with creating an entity or querying for one. But... this post is a little too big to digest. What would really help is a stripped down version of the problem that illustrates the issue. The Breeze zip contains a sample called Doc code that contains a number of unit tests against EF models. If you can repro your issue within this framework, it is highly likely that we can suggest a solution.
      singulars
      1. POBreeze returns navigation properties in the metadata, but not on the entities
      1. USJay Traband
    2. COI'll have a quick look at the sample and see if I can reproduce the issue. I thought that might be a little too much information, apologies. Essentially if you look at the metadata there are various navigation properties described, but when I either query the metadata on the client side, or try and create an entity, the entities apparently have no navigation properties. (Check the example right at the bottom of the post for creating an ExternalTransactionDataSet - metadata shows navigational properties - entity has none)
      singulars
      1. POBreeze returns navigation properties in the metadata, but not on the entities
      1. USAdam
    3. COSo more research and so far I can only get navigation properties to work if I include the inverse key as a property on the objects. This looks like its related in some way to http://stackoverflow.com/questions/16797195/child-entities-not-populated-without-inverse-property. Or is there some requirements we must adhere to when creating uni-directional mappings?
      singulars
      1. POBreeze returns navigation properties in the metadata, but not on the entities
      1. USAdam
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload