Jump to content

Mattcooper

Registered Users - Approved
  • Posts

    9
  • Joined

Converted

  • FusionPro Products
    No

Mattcooper's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter Rare

Recent Badges

10

Reputation

  1. I started to suspect the same thing and have been working the frames down, but I am still at around 80 frames. which has gotten me down to about 4 seconds per record down from 8-10 seconds. Thanks for the comment I will look into removing more of the frames.
  2. Greetings all, We had a merge the other day that had 151 fields and 13,000 records to merge it took over 28 hours to compose the whole job. My question is has anyone ran into a job with this many fields and know away to speed up composing it?
  3. Let me see if I can make it more clear. So the merge file looks like this Letter Report QA FF OUFiller ProFund ProFiller Filler1 Filler2 Back When a book is composed we would get something like this Letter Report1 Report2 QA2 Report3 FF3 Report4 Report5 OUFiller5 Filler1 Filler2 Back So each report has different data based on the FundID so what I meant by duplicate the report page is how will it know I need to use the Report page 5 times. Which I think Step answered with the templete thing which I am about to read up on. Another thing is these pages have to be in a exact order so that is something else that has to be controlled for. Thanks so much Dan I am learning a lot and taking all this to heart.
  4. Thank you Step, You and Dan have given me much to think about on the best way to handle this job. I am going to do some reading and see what comes of it.
  5. Thanks again Dan, You have sparked my thought process. I have not used multiple data files in a job before I was reading a bit on it and it seems like this could help. So if I am following how this would work I would split data sort of like the image below. http://s29.postimg.org/me0e4asvr/mockup.png Than is my merge file I would check each report for a Y/N answer if Y than read the ID for that report and search the Report File for that ID than pull the fields for that ID for the Report Pages text boxes. Only thing I am not fully understanding is how will I tell it to duplicate the report page, but use a different set of fields from the Report File. Thanks so much Dan I am going to read more on this.
  6. Thanks for the reply Dan Korn, I have downloaded 9.3.21 to see if that would change anything sadly it doesn't. The problem is Fusion Pro is doing what it should be doing because each record really is only 1 page because of the way the data is setup. The data is setup so each record is a different page. If we where to make a single record contain all the pages for that record the record would have 400+ columns of data and we would need special pages to handle each different page. For example instead of having a 10 page file like we have now to handle all the different types of books we would need a 70-100 page file which we would have to setup the variables for each different page. This makes upkeep of the document a nightmare say you have to update the header information on the report pages instead of just updating the single report page in the 10 page file you have to update 40 different reports in the 70-100 page file. Sorry about not including the FPI I thought I did I am attaching it to this post. Thanks for the shortened code sometimes I over think simple things. Maybe I am over thinking this whole problem. impo.fpi
  7. Thanks for the reply Step. I have added that information to my signature for the future. I have stripped my document of all the sensitive information and I am attaching it to this reply. We have thought about reworking the data, but we have found that we could end up with over 400 columns per row to handle all the different reports. On top of that we would have to have multiple pages for each report if we say have 20 reports we would have report1, report2, report3 etc columns meaning we would have to create different pages for each one inside the merge file instead of just one report page like we have now. On top of that we would need a much larger OnRecordStart to figure out what pages to turn on and off for each row plus more variables inside the data to help figure out all that. Anyway if you get a chance look over the attachment I think at this point we are stuck without a way to generate the pages than impose them based on a field. Report.zip
  8. Greeting all, After many years of working with Fusion Pro I finally ran into a problem I can't seem to find a solution for. I have a document setup with 10 pages each page is different. The first column in my data set tells me what page should be used and I have written a script that turns on the correct page based on this field. All that works, but the problem is that this data set is building 1000 different saddle stitch books of varying sizes all with custom information. The books can be anywhere from 4 pages to 32 pages in size. I know where they break based on the first field all books start with a letter and end with a back. The problem is I can't impose the document the way it is since every page is seen as a new record the imposition will only impose a single page and not the full range. I can not seem to find anything that lets me define a range of records to impose. I can get the file to compose single PDFs of each book, but this is not the best way because than I have 1000 PDFs to print instead of 1 PDF or 1 VDX file. Speaking of VDX files that as the same problem as the imposition it sees every page as a single record so I can not impose it on press ether. Here is how the merge file is setup Letter Report QA FF rFiller ProFund ProFiller Filler1 Filler2 Back The OnRecordStart Code if (Field("PageType") == "Letter") { FusionPro.Composition.OpenNewOutputFile(Field("Donor ID") + "-" + Field("Donor Name") + "-Qty" + Field("Quantity") + "." + FusionPro.Composition.outputFormatExtension); } if (Field("PageType") == "Letter") { FusionPro.Composition.SetBodyPageUsage("Letter",true); } else if (Field("PageType") == "Report") { FusionPro.Composition.SetBodyPageUsage("Report",true); } else if (Field("PageType") == "QA") { FusionPro.Composition.SetBodyPageUsage("QA",true); } else if (Field("PageType") == "FF") { FusionPro.Composition.SetBodyPageUsage("FF",true); } else if (Field("PageType") == "OUFiller") { FusionPro.Composition.SetBodyPageUsage("rFiller",true); } else if (Field("PageType") == "ProFund") { FusionPro.Composition.SetBodyPageUsage("ProFund",true); } else if (Field("PageType") == "ProFiller") { FusionPro.Composition.SetBodyPageUsage("ProFiller",true); } else if (Field("PageType") == "Filler1") { FusionPro.Composition.SetBodyPageUsage("Filler1",true); } else if (Field("PageType") == "Filler2") { FusionPro.Composition.SetBodyPageUsage("Filler2",true); } else if (Field("PageType") == "Back") { FusionPro.Composition.SetBodyPageUsage("Back",true); } else { FusionPro.Composition.SetBodyPageUsage("Letter",false); FusionPro.Composition.SetBodyPageUsage("Report",false); FusionPro.Composition.SetBodyPageUsage("QA",false); FusionPro.Composition.SetBodyPageUsage("FF",false); FusionPro.Composition.SetBodyPageUsage("rFiller",false); FusionPro.Composition.SetBodyPageUsage("ProFund",false); FusionPro.Composition.SetBodyPageUsage("ProFiller",false); FusionPro.Composition.SetBodyPageUsage("Filler1",false); FusionPro.Composition.SetBodyPageUsage("Filler2",false); FusionPro.Composition.SetBodyPageUsage("Back",false); } Here is how a report may look when generated. Letter Report Report QA Report FF Report rFiller ProFund ProFiller Filler1 Back So my goal is to be able to impose the varying page counts into a saddle stitch template and or create a VDX file that sees the correct number of pages per record. Ether would solve my problem. If I need to clear anything up please let me know I can do everything, but share the data since it is sensitive data.
×
×
  • Create New...