Updating a bunch of forms is one thing.. what fields it updates in those forms 
is another..

Functionality can be impacted to a very large extent if not all the information 
is updated wherever login name type fields are found on those bunch of forms... 
The whole behavior and properties of a row can be affected with changes in 
login names if fields like Submitter, Assigned To, and other application level 
fields holding login name information such as Requester Login Name etc. is not 
changed..

Joe

From: Boyd, Rebecca 
Sent: Tuesday, June 14, 2011 9:20 PM
Newsgroups: public.remedy.arsystem.general
To: [email protected] 
Subject: Re: Bulk Change of login ID

** DLD:SYS:DataWizAction updates a bunch of forms.

Use the Data Wizard Tool to modify one login then check DLD:SYS:DataWizAction. 
It will list all the forms it checked & tell you how any records were updated.


On Tue, Jun 14, 2011 at 4:03 PM, Joe Martin D'Souza <[email protected]> wrote:

  ** 

  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 
  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
     
     

    _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 



  -- 
  Rebecca Boyd
  Application Administrator
  Wake Forest University

  _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 
  _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 



-- 
Rebecca Boyd
Application Administrator
Wake Forest University

_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"

Reply via email to