1 Reply Latest reply: Sep 8, 2016 10:20 AM by Grant Perkins RSS

    Question:  Multiple Lines Horizontally (vs. Vertically)

    Heather Lucas

      I have a report where the Return Reason Description may wrap onto the next line.  This happens when (and only when) the return reason description is longer than the character space provided on the initial line.  Unfortunately, the Multiple Lines functionality within the Advanced tab appears to be map the second line directly underneath the existing data as opposed to moving horizontally.  In other words, my second line is to the left not underneath my first line.  As such, I have created two separate fields, hidden both fields, and then created a third calculated field which concatenates both fields.  However, is there a way to import this field as a single field without the extra steps?  Any assistance is appreciated!

       

       

      Currently, this data is mapped as a Group Footer template as the data is underneath the record and may not exist for all records.

        • Re: Question:  Multiple Lines Horizontally (vs. Vertically)
          Grant Perkins

          Hi Heather,

           

          Assuming you have managed to stop the Footer repeating for other detail records where it does not apply I suspect that your approach is as clean as anything else.

           

          The only other thought that occurs to me, based on your description and what I can see form the images posted, would be to take the entire block of 2 lines, including the code, and "slice and dice" it to extract the code and the description. In effect it would doing much the same as you have already done so if what you have works for you in all instances there is not a lot of point in doing anything differently.

           

          Traditionally that sort of programming decision (to offset the "extension" part of a field)  taken for an original report is extremely rare in my experience. Similar thing s can happen with PDF files (is this a PDF original?) . If things get really unpleasant, especially useful with awkward PDF files, there may be some sense in looking at the first pass extraction and deciding whether the best approach would be to just do a basic extract with every line as a single field. Then process the result to an output file perhaps removing all leading spaces from every line and then apply the required modelling to the resulting file rather than the original input file.

           

          However, in this case that would not really move you any further forward and would not save any effort for intermediate steps in your process.

           

          Does you solution work for you or has it left residual problems that you still need to address?

           

           

          Grant