Hiding Inverse Relationship entries project in DTL graphics

Question

Question

Steve Pisani · Apr 1, 2022

#DTL #Interoperability #Ensemble #InterSystems IRIS

Hi

I have an a Ens.Request subclass (Invoice) that has a relationship property to another persistent class (InvoiceItems), with properties of its own and the inverse relationship defined referring back to Invoice.

When building a DTL with these classes, the Relationship’s inverse relationship (Invoice, within InvoiceDetails) is displayed.

Can this be hidden ?

thanks

Product version: IRIS 2021.2

Discussion (5)1

Log in or sign up to continue

Stefan Cronje · May 6, 2022

Hi,

Apologies. My mind must have been in the wrong place. I was looking at it from the Ensemble message browser's side for some reason.

0 0

score 0 · Answer 1 · 2022-04-28T01:39:48-04:00

Stefan Cronje · Apr 28, 2022

I don't know if this will work, but did you try setting XMLPROJECTION="NONE" on the inverse property?

0 0

score 0 · Answer 2 · 2022-04-28T01:48:27-04:00

I didn't actually,.. , because, whenever I've used persistent classes with relationship properties and projected instances in code (using the XML.Adaptor) - I've never seen the inverse property show up in the XML.

I could try it though...

score 0 · Answer 3 · 2022-04-28T10:12:01-04:00

I dug around a bit.
It works from the dictionary classes to create the table being displayed.
I did see in there that if you add an XData block to your class called "FormDefinition" and omit that property, then it will not display it.

Have a look at this:
InterSystems CSP AutoForm

I also saw that the table generator goes up to 4 levels deep of recursive processing of a message's properties.

score 0 · Answer 4 · 2022-05-05T20:40:22-04:00

Hi Stefan,

I wonder what led you to determine that the DTL is being drawn by using InterSystems CSP AutoForm (%CSP.Util.AutoFormGenerator), because, I added the XDATA block to the child class to include only the child class's properties as suggested, (and omitting the inverse property):

XData FormDefinition
{
<field property="childPropA"/>
<field property="childPropB"/>
...
}

but the inverse property, in the DTL, still appears. (also confirmed defining XMLPROJECTION="NONE' on the inverse relationship property also has no effect)

looking at %CSP.Util.AutoFormGenerator, I see my XDATA block definition is being checked, and honored, returning as it should, the list of properties for a form - but this does not seem to end up effecting the DTL Wizard.

Steve