Re: [Arsperl-users] ars_SetEntry usage when updating remedy incident
Brought to you by:
jeffmurphy
|
From: jeff m. <jcm...@je...> - 2008-04-26 13:36:12
|
On Apr 26, 2008, at 8:13 AM, Ravi wrote:
> ars_SetEntry($ctrl, $schema, $record, 0, 536871244, 3) || die
> "ars_SetEntry(User): $ars_errstr";
>
> But if I set a variable $updRemString and run the ars_SetEntry, it
> gives
> me an error as shown below
> $updRemString = "536871244, 3"
> ars_SetEntry($ctrl, $schema, $record, 0, $updRemString) || die
> "ars_SetEntry(User): $ars_errstr";
>
The first (working) line is:
ars_SetEntry($ctrl, $schema, $record, 0, 536871244, 3)
The second (nonworking) lis:
ars_SetEntry($ctrl, $schema, $record, 0, $updRemString)
which is equivalent to:
ars_SetEntry($ctrl, $schema, $record, 0, "536871244, 3");
In other words, you are only passing five, instead of six, parameters.
The final parameter is
a single string parameter, instead of being two numeric parameters.
You could try this:
ars_SetEntry($ctrl, $schema, $record, 0, split(",", $updRemString) );
|