Hi!

I recently reported (2017-11-01 18:22) what appeared like a bug in regards to dataclass lineage. Since then I've discovered other issues which appear to be inconsistencies to me. It could also be I don't have a good understanding of how dataclasses are meant to perform. Either way, I would definitely appreciate some advice.

Issue 1. Accessing detailed information regarding Runs
I am trying to query information regarding the inputs and outputs of runs. When I try to customize the grid view for a specific datclass and navigate to Inputs/Runs/All and then try to expand any of the fields with the little plus sign next to it, I get an error. For example when I try to expand Inputs/Runs/All/DataOutputs I get the error "The column 'Inputs/Runs/All/DataOutputs' is not a foreign key!". I seem to get this "foreign key" error if I try to expand any "4th level" fields under inputs or outputs (i.e. anything inputsORoutputs/x/x/x doesn't expand even if it has the + sign next to it). I tried to examine these same fields under the schema browser. Once again for any of these 4th level fields with a + sign next to them the "Description" indicates that this field is a lookup or identifier which should link to other fields/tables. However when I click on the +, the table expands like it is trying to load in the field information, but nothing happens and I just see "loading...".

Issue 2. Lineage inconsistent when updating existing records
I have created a very simple dataclass called testlink. When I update the lineage for existing records there is inconsistent behavior between information displayed in the datagrid view and the information displayed in the single record details view.

For example I initialize three records, where test41 has the input(parent) test40 and output(child) test42 (image1). The parent information within the single record view and datagrid (utilizing the Inputs/Data/testLink field) are consistent and correct. Note I'm not discussing the Outputs/Data/testLink in the datagrid view, as none of the correct information seems to be making it into that field at any point as I previously reported (2017-11-01 18:22) . If I create a new record that lists an existing record, which already has child data, the new and existing child are both listed under "child" for the existing record and the new record has the appropriate parent. However, if I create a new record which lists an existing record (which already has a parent) as a child, then a discrepancy arises where the existing record only lists the new record as the parent in the single record details view, but the datagrad shows both the previous and the new record as parents of the the existing record. In addition the previous parent still lists the existing record as a child in the single record view. For the example I've given, test41 has test40 as a parent. I then created a new record test43, which lists test41 as a child(dataOutput). Now test41 shows test40 and test43 as parents(inputs) in the datagrid view (image2) but only test43 in the single record view (image3). However, test40 still lists test41 as a child in the single record view (image4). Ideally I would like all previous lineage relationships to be maintained and not replaced unless explicitly done so (which is what the datagrid view seems to be doing). But either way it seems like the datagrid view and the single record view should provide the same information.

Would definitely like to know if these are indeed bugs, or if my understanding of how dataclasses should perform is flawed.

Thanks!
Camille