Custom Query View showing up in Constituent Interaction rather than main Interaction section in Ad-hoc Query

Dear all,

I've built a very simple Query View, called TWS - Interaction Extras, using the SDK, very similar to many we've built in the past. However, when I load it into the Catalog, it appears in the wrong place in the Ad-hoc Query editor. When I choose a Query of type Steps/Interactions, it doesn't show up in the main list of sub-nodes, but rather hidden under Constituent Interaction.

5c84e3b9110db334c22cf99d67489281-huge-im

The <RelationshipOperations> tag is as follows:

<RelationshipOperations>
<AddToParentView Field="ID" ParentView="V_QUERY_INTERACTION" ParentViewRelatedField="ID" PathAlias="TWS - Interaction Extras" DisplayAliasResourceKey="$$tws_interaction_extras"/>
</RelationshipOperations>

What am I doing wrong?

I've attached the full XML, complete with some debugging info, sorry.

Kind regards,

David.

TWS.QueryView.InteractionExtras.xml

Comments

  • @David Wanless

    I would change the parent view to V_QUERY_INTERACTIONALL and it should be in the correct location. I got that view name from this query in SQL:


    SELECT * FROM QUERYVIEWCATALOG WHERE DISPLAYNAME = 'Steps/Interactions'

  • @Nick McGinnis
    Dear Nick et al,

    Brilliant. Thanks, Nick. That did the trick, for Queries of type Steps/Interactions.

    However, for Queries of type Constituent, the 'TWS - Interaction Extras' View/node doesn't seem to be present at all. Normally, Query Views/nodes attached to, say Constituents, show up in Views like Steps/Interactions. Has anyone any ideas how to get my new View to show up under both Steps/Interactions and Constituents?

    Thanks,

    David.