For Each - How do you quickly find the end for each?

[johndanter]

Hi folks,

As the subject says, I can see For Each sections in my template but I'd like to quickly know where the End is. This isn't easy to do in MS word

I have quite a complicated template with many repeating sections
How do others do it?

Thanks

John

 

[Mike Mackinnon]

Are you talking about nested "For Each/End"s?

 

[jileto]

Hi folks,

As the subject says, I can see For Each sections in my template but I'd like to quickly know where the End is. This isn't easy to do in MS word

I have quite a complicated template with many repeating sections
How do others do it?

Thanks

John

Use the Field Browser tool. It'll show the blocks with indents. I use it together with the Validation tool.

BUT, the Field Browser tool only works if you place your code in "fields". Doesn't work with the free-hand stuff. So make it a habit to put any code in fields.

 

[johndanter]

Are you talking about nested "For Each/End"s?

Yes mate.

Thank all. I'll try it

 

[Mike Mackinnon]

Hey guys,
Not sure if this is applicable to what you're doing (probably not) but I had a recent example where I was trying to group items within the RTF template using multiple 'for each' sections. It became difficult as my 'nested' for-each groups were not working properly. Anyway what I did was change the underlying JD Edwards UBE to use subsection joins for the report instead of handling it within the BI Publisher RTF template. This changed the actual layout of the XML file and made it much easier to process as it 'looked' more like how I wanted the report and made the RTF much easier to design.

I don't think this is what you were talking about but thought I would pass along just in case. Anyway, bottom line was that I found it better to handle better within the UBE rather than trying to code it within the template. Sorry if it's not what you were dealing with but just thought I would put it out there.

 

[johndanter]

.....what I did was change the underlying JD Edwards UBE to use subsection joins for the report instead of handling it within the BI Publisher RTF template. This changed the actual layout of the XML file and made it much easier to process......

All helps mate. I actually had to do this with R31415 WO Print for multiple WOs yesterday. Total XML mess that thing produces