Submitted by Anonymous on 2008/12/07 15:51
Hello,
 
I don't see anything about HTML exporting in the user manual.
 
The example template looks pretty cool. It looks like you just put your fields in brackets {MyField}
 
In the invoice example, there is no detail. Most clients are going to demand that. Is there a way to to loop through child items? Or a way to create a parent level item that automatically combines text from the child items?
 
Thanks,
Mark
 

Comments

>a way to create a parent level item that automatically combines text from the child items?
 
this is planned, if I'm not mistaken... Don't know for when though.
 
Some related Mantis issues/suggestions  :
 
 
 
 
(Must say that 177 would be very sexy...)
 
 
But maybe did you have something else in mind ? Did you have a look at the HTML export functionnalities ?

Anonymous

2008/12/07 17:05

Permalink

I guess I should have used the word "export" in the subject line. The suggested mantiss items relate to how the system views its HTML editing form, not to the export technology.
 
I was thinking of how the data gets exported to an HTML page. Currently you can (1) accept the defaults and print a single page is which is essentially a grid consisting of all items that you have selected before output.
 
Or you can (2) use a custom HTML export template. The example given is to export to an HTML invoice.
 
The custom HTML export template, however, only works for one item (whichever one you're sitting on when you do the export). If you were making an actual invoice, you would probably want to include sub-items that explain the make-up of the invoice. Of course, you could lump all that into one text field, but that would
 
So the first (1) approach lets you export multiple lines, but gives you little control. The second approach (2) gives you more control, but only exports a single record (item).
 
And of course, if you were batch processing, you might also want the ability to export html files at a time (like for monthly invoice processing). This would be an extension of the second (2) approach.
 
What would be desireable would be the ability (3) to repeat child items within a report. I suppose this would get you into the area of banding which would substantially increase the complexity of the template (you'd have to indicate where a band would start and end, for instance).
 
Thanks,
Mark
 
 
 
 

  • It is already possible, but I need to document it better.
  • You can also use Access to link to your IQBase and use the nice Access report designer to design your reports. IQ is all about inter-operability.

Anonymous

2008/12/08 01:37

Permalink

Having to pay for Access, and get up to speed in it, just to get a particular output seems like a rather challenging solution.
 
Admittedly it would be impossible to duplicate the report generator in Access (which when I was working with it I felt was better than the much proclaimed CR generator).
 
-- Mark
 

Pierre_Admin

2008/12/08 07:38

Permalink

Perhaps I wasn't perfectly clear... IQ support HTML based templates AND Access. You choose the one that suits you best.

Anonymous

2008/12/11 13:41

Permalink

> It is already possible, but I need to document it better.
 
Er, could I have a few hints? I've worked in CR, access reports, html templates, other report generators. My last job in VB involved rewriting the print output. Maybe with some quick guidelines I could figure it out ... maybe even write it up.
 
The reason I find this issue compelling, is that without it there is no way to share information on machines where I can't run IQ (linux boxes).
 
With it, you could do neat things maybe like make your own online photo album, generate monthly statements, create portable bookmarks, carry your own reference material, etc.
 
Thanks,
Mark