Some guidance in using nested detail tables

OL Connect Professional Designer
1

Hi,

I need some help in using nested details tables in Designer.

I already have a datamapper, which extracts the data from an xml source in the way I need it. This gives me a data model similar to this (greatly simplified):

Record

  • Items
    • stocks

There is no problem to list all items for the record, but I need also all the stocks for the item.

Best regards

-i.

1 Like
2

Tech support told me that it is only possible via scripting and not by nesting dynamic tables. Should be available around version 1.3.

3

iiliev,

You may want to try changing your data mapping so that it uses detail tables at the same level under each record.

The (simplified) structure would then look something like this:

Record

  • Items
  • Stocks

In the Stocks table, you should simply add an additional field that contains the parent Item’s ID. This will allow you to use simple detail tables in the Designer without having to fuss with complex scripts.

4

Thanks for the answer. It’s also written on the help page about dynamic tables.

But it would be great to have a sample, just to see, how the tech support would do it with a script… That was the goal of my question :slight_smile:

Greets

-i.

5

Thanks Phil,

It wouldn’t be a problem to flatten the xml structure and keep the relations through parentIDs in the data mapper. But I still don’t know, how to filter the view, based on these parentIDs, like for example:

  • Item1-data
  • item1-stock1-data
  • item1-stock2-data
  • item2-data
  • item2-stock1-data
  • item3-data
  • item4-data
  • item4-stock1-data

and so on…

greets

-i.

6

I am not quite sure what you mean. If you can attach a sample file and a visual snapshot of what you want to produce, I could take a stab at it.

7

iiliev

we are trying to do the same thing you are trying to do. Did you ever get a scripting sample to see how to go about it?