In the future (and in general cases where data structure isn't known), a simple 
use Data::Dumper;
warn Dumper \%ARGS;
warn Dumper $ARGS{LineItem};

[download]
would have show that it was an array ref, leading immediately to the @{$ARGS{LineItem}} solution.

Also, in mason you can do this: 
<%args>
        $LineItem=>[]
</%args>
<%init>
  warn join ":", @$LineItem;
  ...
</%init>

[download]
That takes care of the case where just one LineItem form element exists. Using that syntax, you'll still get an array ref. Using the above $ARGS{LineItem} syntax you'll get a scalar, which will make the @{$ARGS{LineItem}} solution error out.

In reply to Re^2: Parsing cgi variable lists by davidrw
in thread Parsing cgi variable lists by inblosam

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.