Can't add a filter condition for a table that is an extension of our request table - a dot walking problem?

[aansell]

Hi,

Any help with what I think may be a dot walking issue   - or an explanation of my problem would be most appreciated.

I have created a new table called 'Hardware Request' that is an extension of the request table. The table just adds a couple of extra fields on top of the request table and I am trying to modify the 'My Groups Work' module to include this table but do not seem to be able to access any of the fields that are in the request table. My assumption is that I would be able to dot walk to any field in the table (Request) that my new table was extended from i.e.   Hardware Request.Request.Request state - but this doesn't seem to work.

Here's a screenshot below - does anyone have any ideas where I am going wrong?

Thanks,

Arthur

[aansell]

Hi Matt,

There is a parent child relationship. My new table 'hardware request' is extended from 'request'. I tried using the parent filters but it's not intuitive. I have not got it to work yet - although I managed to select 'Parent.Request.Request State' but I don't think that is correct. I don't seem to be able to make the selection that you suggested. My goal is to try and exclude the 'Resolved' states and here's a screenshot of where I am at following your suggestion.

Arthur

[Greg42]

What you can also try is to build that filter in the list view - might be easier to test. When you have an expected result you can use URL (from Arguments:) or try to rebuild it with list of records.

Regards

Greg

[aansell]

Thanks Greg - that sounds like a good option, I will give it a go.

Cheers,

Arthur

[aansell · Accepted solution]

Hi Greg,

That looks like the solution - so many thanks for the guidance. I built the query as you advised and then copied the url & created another module with the URL (from Arguments:)   (screenshot below if anyone needs something similar. Note: make sure you specify _parent or _blank depending on where you want it to open. If you leave the window name blank it does not default to _parent - at least not in Kingston Patch 1). I need to do some more testing but it all looks good so far.

Best regards,

Arthur