I hope this is what you want/need so I will show how to build a detail table with a sub-detail table in it. Look at the screenshot below. I have used the detailS and nested detailDetails as they represent what I think you want:
I first Inserted a dynamic table on a new section using the grid like ison in the top banner with a yellow arrow in it:
Then I selected all the fields I wanted at the first level of my detail table (it could look like it is hanging while you go from step to steps but it is normal, you have LOT of fields, so be patient ;):
Atfer that I added a new row by clicking on the upper right green plus sign in the previous image which will display a list of availalble detail table (sorry, unable to do a screenshot of the pop-up choices) and I chose detailS.detailDetails. I then proceed by adding the fields, from that nested detail table that I wanted by clicking on the green plus sign on the same newly added row (at the moment of this writing, it seems to display a list of the fields available from that nested detail table but in reverse order , I will open a ticket for that but thought you should know):
Once you have done thatm the rest is up to you with CSS. Of course in my example I only select 2 fields from each detail but that is to keep the example simple.
I think i understand how standard detail table can be inserted but try Your way also today.
My question is, how to make the table header (in our example the service header) to move to next page when there are more records then we can fit on page 1. Like service header should be carried forward next page.
You may want a product line to be repeated when its attributes run over multiple pages. In order to get that repetition, first add an extra row in the Dynamic Table Builder, and link it to the detail table. Then change the “Initial” setting to Before a page break, After a page break, or before and after a page break (All).
Unfortunatelly i will have to rebuild/recreate whole my script table inside this.
What I need to understand now, to continue working on that is how to replace this dynamic table record depending of data mapper field. This is regarding inner detailS.details table.
For example i can have many type of record depending of “RecordType” field inside data mapper.
For example when “RecorType” will have “D” then i will have to display 5 fields and apply other styling.
For example when “RecorType” will have “DH” then i will have to display 2 fields and apply other styling.
Once you have done the basic for you detail table, the best way is to go on the source tab and edit your detail table.
Manually reproduce the nested row and adapt it to what you want display when it fits your RecordType. See code below as an example. You 'll notice i make use of HTML tag colspan which allow for a field to span across multiple ones.
As you see, I have setup 3 rows, each with their own class that i will use (the class) to remove the row I don’t need at run time (script below). Each row has its own number of fields and use colspan to compensate for the difference between the highest number of fields VS the others.
This is a script that looks for class DType. I couldn’t find your RecordType so i use the BillType but the idea remains.
Sorry the data mapper field was called “Indicator” not “RecordType” (RecordType just as example)
So i will just apply some class name to my record which i develop and add standard script based on class selector and show/hide them depending of data mapper field? Looks good, need to try this tomorrow.
I just want to add that if you change the scope of the script to “each matched element” (in the options panel at the bottom of the script editor) you only need the following:
if (this.record.fields.BillType != 'D') this.remove();
Note that “this” represents a table row, and “this.record” represents the detail record associated with that table row. What makes this especially useful is the fact that it also works for rows in nested tables.
FYI, if you start typing the code provided by @Sander, once you type the this.remove();, the auto complete will not propose the remove() option. I will report this. I know it did made me beleive that it wasn’t an option.
I can’t explain why hide() behaves differently than remove() in this particular case, but I’m happy to hear that you managed to figure out what was going on and that you found a workaround.
I suggest you open a ticket with our support department via our website. Then support will be able to look at why .remove() causes an issue with our R&D dept.
So when I try to change the width of REF# colum in designer, then automatically the size of Service Name also change to same width. It seems to be related but how to change that to different sizes
How to set whole table columns size to be independent?
You can’t. By default, the first displayed row will set the width for all columns.
I suggest you you had a <th> row that will define the width of all columns. You can make it with no height so it doesn’t show. That is the one that’ll define the width of all your column.
Now if you really need to have various size columns that have each their own width and arrangement separate from other row, then you’ll have to programatically build your table as to have multiple tables inside the original table. But by doing this, you won’t be ble to use the table population automation of Connect. You will be the one building the whole layout for each row.
First, why do you have a colspan=“0” in your first row?
As for opening a technical session, I already propose you open a support ticket with one of our technicians in a previous post.
, I will open a ticket for that but thought you should know):
