Control for "detail of detail"

anna_kalligerou

I need a control for screens with a "detail of detail". Any ideas??? Thanx in advance

Arhontis

Hi,

Wellcome to the forum...

Could you be mere specific on that "detail of detail" thing?

anna_kalligerou

You see I have a form that has the following structure:

Header
Detail
Detail of previous detail

Is that a liitle bit more clear?

Timo_Lässer

Make a Main-/Subform where the Subform is also a Main-/Subform.

Form A: Card form with a Subform control (Form
Form B: Table form with a subform control (Form C)
Form C: Table form

anna_kalligerou

Thanx, I will try it ASAP!

PrebenRasmussen

Timo, what planet did you arrive from? :-)

This is not possible in Navision, has never been!

Timo_Lässer

<OffTopic>

PrebenRasmussen wrote:

Timo, what planet did you arrive from? :-)
[...]

Sorry, this is top secret, otherwise the NASA deports me back to home
</OffTopic>

PrebenRasmussen wrote:

[...]
This is not possible in Navision, has never been!

Upps, I didn't try this anytime - it was a thought which crossed my mind.

PrebenRasmussen

he he... 8)
Glad that you understood the joke!

Shenpen

It IS possible, just not comfortable.

1)You have to write a function to the subform that returns the primary key or any other data you need of the record.
2)Create a function in the second subform that issues a SETRANGE-FIND or GET from parameters it receives.
3) Create a button or menu item to the main form that calls the first function, and then call the function on the second form. A menu item is preferred because users will hate this solution, but at least you can assign a keyboard shortcut to the menu f.e. Ctrl+R as "refresh".

Luc_VanDyck

I guess this is the example you need:
Multiple Subform Sample -> uses Single-Instance Codeunit
New Multiple Subform Sample -> uses OnTimer-trigger

Shenpen

My suggestion is that all these tricks are too complicated for users, they will get a big, confusing form.

My suggestion is: just use flowfields.

For example, you have a project form, where the header is the main data for the project and the lines are the phases. There would a COUNT flowfield for every line, that would say how many steps a give phase has. As the normal flowfield behaviour, this would bring the normal Drilldown field for your Steps table. From there also could be a drilldown to Tasks etc. ...