Jason,
Another trick, create a final column labeled LAST and put a constant value
in each cell. (I use 1). Then each row has a guaranteed value and you just
don't map the column to any field. Remedy doesn't care whether you have
more columns than you need, only if there are less columns.
If you save the file as .csv using Excel, Excel puts all of the text fields
within quotation characters ("). If you are still having problems, open
the .csv file with Notepad to try to determine what might be causing your
problem.
Ron Fariss
AIG Technologies
Remedy & TelAlert Administration
Work: (713) 831-2365
Cell: (281) 782-0979
Mike White
<[EMAIL PROTECTED] To: [email protected]
ON.COM> cc:
Sent by: "Action Subject: Re: Remedy Import -
Limits to 15 records
Request System
discussion
list(ARSList)"
<[EMAIL PROTECTED]
ORG>
07/31/2006 08:51
AM
Please respond to
arslist
Length probably changed after the 15th record (column populated for rows
1-14, but not for 15th, or vice-versa). I haven't seen your data, but this
is where I'd look first.
Matt makes good points about data condition. Hard returns result in two
(or more) records where you intended one. Field mapping would misalign.
Imbedded commas in text could be problematic, too. (.csv files are
comma-separated).
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
"Carey Matthew
Black" To:
[email protected]
<[EMAIL PROTECTED] cc:
COM> Subject: Re: Remedy Import
- Limits to 15 records
Sent by: "Action
Request System
discussion
list(ARSList)"
<[EMAIL PROTECTED]
ORG>
07/31/2006 09:43
Please respond to
arslist
Jason,
If the columns are "empty data values" in the file. Then do not map
them in the import tool. (It might help.) However, apparently, some
rows have data, or null data, defined for them.
I have seen such behaviour when the csv file is edited with Excel.
Another possible point of confusion is how "hard returns" are dealt
with in csv format. Some editors write them as hard returns and thus
break up the single line format of csv.
Keep in mind that filters that fire on merge can look at data supplied
to display only fields too. (A good, old school, way to do some
signaling for data merge work IMHO.)
Then again... this could be as "simple" as a bad client install, or a bug
too.
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.
On 7/31/06, Jason McDonald <[EMAIL PROTECTED]> wrote:
> ** But in that case how does it work for the first 15 records?
>
>
> On 7/31/06, Mike White <[EMAIL PROTECTED]> wrote:
> > It's caused by variable-length records. Remedy Import doesn't tolerate
> > them too well. When we import from .csv, we make sure the last column
is
> > fully populated - moving columns if necessary. This will fix/set your
> > record length.
> >
> > Mike White
> > Office: 813-978-2192
> > E-mail: [EMAIL PROTECTED]
> >
> >
> >
> > "Jason McDonald"
> > <[EMAIL PROTECTED] To:
> [email protected]
> > COM> cc:
> > Sent by: "Action Subject: Remedy Import -
> Limits to 15 records
> > Request System
> > discussion
> > list(ARSList)"
> > <[EMAIL PROTECTED]
> > ORG>
> >
> >
> > 07/31/2006 09:15
> > Please respond to
> > arslist
> >
> >
> >
> >
> >
> >
> > **
> > Hi List,
> >
> > Once again I seek your advice.
> >
> > This pertains to Remedy 6.0.3.
> >
> > I am really getting irritated when trying to import data via the Remedy
> > Import Tool. Irrespective of what form it is and how much data I have
in
> > the CSV file, Import always breaks at 15th record with the message -
> > "[Record 16 of XX] : Unable to import. Found 30 columns, expected 32"
> >
> > Note that it always says that it found X-2 columns when there are
actually
> > X columns in the CSV file.
> >
> > In order to import all the records, I have to keep on deleting the
first
> 15
> > records from the csv file so that the import can process another 15
> > records.
> >
> > Can anyone help on this?
> > Thanks.
> > __20060125_______________________This posting was
> submitted with HTML in
> > it___
> >
> >
>
_______________________________________________________________________________
> > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
> >
>
>
> __20060125_______________________This posting was
> submitted with HTML in it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
