<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hello.
<div><br>
</div>
<div>I'm looking for a solution to my conundrum (aren't we all?)... We have a cabling request spreadsheet that we want to webify and fold into a ticketing and inventory tracking system. I've got RT 4 and AT 2 working fairly well together now, but I'm running
into an issue trying to get the new ticket form for the cabling queue to work properly. For each ticket there will be anywhere from 1-20+ cable runs on the ticket, and they each need a source, destination, and other info attached to them. This is obvious
on a spreadsheet, but I'm having a hard time translating it into Custom Fields. so something like</div>
<div><br>
</div>
<div>environment, source rack, source equipment, source port, destination rack, destination equipment</div>
<div>1e, 1sr, 1se, 1sp, 1dr, 1de</div>
<div>2e, 2sr, 2se, 2sp, 2dr, 2de</div>
<div>3e, 3sr, 3se, 3sp, 3dr, 3de</div>
<div>...</div>
<div><br>
</div>
<div>As you can see the number of discreet CFs quickly gets out of hand with something like this. I'm trying to avoid uploading attachments as separate entities but an attachment (simple Excel spreadsheet for example) that was translated into CFs would work.</div>
<div><br>
</div>
<div>Thank you for any suggestions helping me make this work correctly.</div>
</div>
</body>
</html>