Hi,
The tool will get all char/diary/status-history data from the server,
where you can specify a max-length for your char-fields and skip
diary/status-history if you like.
It will then match the data against the conversion list in this fashion:
1. Exact match ('Data' = "fromuser1").
2. Quoted matches ('Data' LIKE "%'fromuser1'%") and the same thing with
double-quotes. Can be disabled.
3. List matches with separators CRNL, NL, tab, comma, semicolon, colon and
pipe. This can also be disabled.
If anything is found, the records and field will be marked as changed, and
the tool will do an ARMergeEntry() back to the server, with changed fields
only for that record.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Actually this would be a better tool then as your tool might possibly be
> doing an EXISTS IN comparison on fields smaller than 255..
>
> Joe
>
> -----Original Message-----
> From: Misi Mladoniczky
> Sent: Wednesday, June 15, 2011 6:13 AM Newsgroups:
> public.remedy.arsystem.general
> To: [email protected]
> Subject: Re: Bulk Change of login ID
>
> Hi,
>
> The rrrLoginConv tool performs the change on everything in the system,
> including:
> - Exact Matches on any char-fields smaller than 255 chars (size
> configurable)
> - Quoted user names in fields such as the 60xxx fields for dynamic
> permissions (can be skipped)
> - Status-History entries (can be skipped)
> - Diary-Entries (can be skipped)
>
> It takes a list of any number of user names to convert.
>
> You can perform a dry-run first to see in which fields it finds matches to
> convert.
>
> It does NOT change Modify Date or Modified By.
>
> Best Regards - Misi, RRR AB, http://www.rrr.se
>
> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10):
> * RRR|License - Not enough Remedy licenses? Save money by optimizing.
> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
> Find these products, and many free tools and utilities, at http://rrr.se.
>
>> Yes, Data Wizard considers existing tickets, and field id 2 and 4.
>> However,
>> it does not recognize any custom fields. It runs perfect on 1:1 basis.
>>
>>
>>
>> http://www.remedycloud.com
>>
>>
>>
>> From: Joe Martin D'Souza [mailto:[email protected]]
>> Sent: Tuesday, June 14, 2011 4:04 PM
>> Subject: Re: Bulk Change of login ID
>>
>>
>>
>> **
>>
>>
>>
>> Does the Data wizard consider existing tickets and the values of field
>> 2,
>> 4,
>> and other login name type fields even if they are custom?
>>
>>
>>
>> If not you may have to write a DB script to get this done.. I had done
>> it
>> using a DB script to mass change login names in a system a few years ago
>> long before the dawn of these nifty utilities that are now being bundled
>> over the past couple of years or so...
>>
>>
>>
>> Joe
>>
>>
>>
>> From: Boyd, Rebecca <mailto:[email protected]>
>>
>> Sent: Tuesday, June 14, 2011 8:23 AM
>>
>> Newsgroups: public.remedy.arsystem.general
>>
>> To: [email protected]
>>
>> Subject: Re: Bulk Change of login ID
>>
>>
>>
>> ** I've used the DLD:SYS:DataWizAction form to bulk update login names.
>> Open
>> it up & look at it. If you've used the Data Wizard Console to make any
>> changes, you can search & see the records.
>>
>> Here is what I did:
>>
>> Exported the users that needed changing from CTM:People.
>>
>> Created a csv file.
>>
>> Imported the csv file into DLD:SYS:DataWizAction.
>>
>> Then - & this is where it gets funky - I used a program called
>> AutoHotKey
>> to
>> run through the everything I'd imported into DLD:SYS:DataWizAction.
>>
>> The reason I used AutoHotKey is because I could make it wait for the
>> update
>> action to complete before moving on to the next record. A colleague
>> recommended this & help me set it up.
>>
>> HTH,
>>
>> Rebecca
>>
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Jun 14, 2011 at 7:09 AM, Michael Burton
>> <[email protected]> wrote:
>>
>> **
>>
>> Morning,
>>
>> Just wondering if anyone has experience of a bulk update of people's
>> login
>> ID's. Basically we configured our system to use people's email addresses
>> as
>> their User Name. The obvious advantage of this is that your are
>> guaranteed
>> a
>> unique entry for each employee. Authentication takes place against our
>> AD
>> servers.
>>
>> So we are now in the position that due to a company purchase, we are
>> going
>> to have to change everybody's email address, and as such, regardless of
>> short term work arounds we might be able to put in place, each users
>> login
>> ID will need to change too.
>>
>> I've had a dig on support.bmc.com and found questions about using DMT,
>> but
>> it's not designed to do it.
>>
>> It would seem that the best option is to use the Data Wizard Console,
>> but
>> that only works on a 1:1 basis, but it does do the job and updates
>> everything rather than just the CTM:People form and/or the User form. Is
>> it
>> just a case of bite the bullet and crack on with it via the DWC?
>>
>> Cheers
>> -
>> Mike
>>
>>
>>
>>
>>
>>
>> --
>> Rebecca Boyd
>> Application Administrator
>> Wake Forest University
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
