M.B.

I am sure there is a way to fix these records. And I would guess that
one way would be to do something like this:

1) Export three columns of data from the effected records to an ARX or CSV file.
    Field 1 (maybe called 'Request ID', 'Entry ID', 'Call ID' or some
other name)
    'reported date'
    Field 3 (maybe called 'Create Date', 'Create-date', or some other name)

* Note if you do not want to set 'reported date' = 'Create Date' then
pick any other field you want from the existing record and export that
data instead of Field 3.

2) Use the Import tool to *update* the existing records.
    Select the form, select the file that you exported above, and "Map all"
    * Note: Configuring the Import tool to update existing records is
found in File(menu) --> Preferences (menu item) --> Duplicate Request
ID (tab) menu of the import tool.


Barring any strange Merge filters on the form then that simple process
should work.

-- 
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.




On Fri, Aug 15, 2008 at 1:16 PM, MCrawford <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> About 100 tickets have been created with blank/null reported dates.
> This is causing issues with reporting.  Most of the tickets were
> associated with a single user.  I have removed and re-created his
> account, and the error appears to be resolved.  However, I need to
> know if there is a way to fix the erroneous tickets?
>
> Thanks,
>
> M.B.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to