I didn't try mapping $DEFAULT$, I just had a value in the field, and it wasn't checking the default because I only told it to get it from the LDAP record. My bad there. My structure (which seems to be working) is now this: <Hour>:00: Escalation that imports new records containing phone #s. <Hour>:05: Escalation that imports new records NOT containing phone #s. <Hour>:10: Escalation that updates existing records containing phone #s. <Hour>:15: Escalation that updates existing records NOT containing phone #s. Filter (firing on Modify where 'Last Modified' = AR_ESCALATOR) that does some data gathering from other forms, and does various set fields to more completely populate the user record (Cost Center, Manager's name, etc.). Still fleshing this one out, but I'm most of the way there. Rick _____
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Monday, May 14, 2007 2:19 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7/LDAP not importing some records ** Does this happen only with $DEFAULT$ mapped to a field or does it happen with constant values mapped to a field? By constant values I mean if in case we want to put a value of lets say 'x' to a field and we type x into the value part on the import tool mapping, will it fail? I may have to do something like that while importing people information into CTM:People using a excel file format that BMC gave me with a few merge filters, and they have instructed me to put constant values such as 0000000000 in a field and PPL000000000000 in another.. I'm wondering if I would need to define filters in order to input these values? On a slightly related note (mass importing users from external sources), has anyone else used that utility that comes with 2 def files: 1) PeopleDataLoad.def 2) PeopleDataLoad_APS.def (optional if you have the approval server installed) Any shortcomings using this? One inconsistency that I noticed is that the filters defined on MERGE, formats the phone numbers in the format +1 999 888 8888 Ext. 7777 while the out of the box submit/modify active links if entering the data using the administration interface formats it as 1 999 888 8888 (7777). The outputs described happens in the event the country code is 1, Area code is 999, Local phone is 888 8888 and Extension is 7777. As this would bring about data to be formatted differently when imported, I've disabled the MERGE filters that format phone, fax, pager numbers after importing the above def files. I was wondering if anyone has noticed any other discrepancies in these def files if anyone else has used the same.. Rgds Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Rick Cook Sent: Monday, May 14, 2007 4:08 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7/LDAP not importing some records ** Yeah, I've seen that the Modify Escalations seem to update all records, because I haven't found a effective and efficient way to check for changes, and it would probably take almost as much time to do the check as it would to update the data anyway. Thankfully, we're under a thousand, so actions to submit and/or modify all records only take a minute or so. The data is fairly volatile, so I'll try updating it every few hours during the day. It shouldn't be a noticeable impact, and if it is, we can always back it off to an acceptable balance. Thanks again! Rick _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Roger Justice Sent: Monday, May 14, 2007 12:57 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM 7/LDAP not importing some records ** When I did the push qualification I did a RequestID != Remedy Login. My Vendor request ID is mapped to the network login. The only potential problem is that if you have 5000 entries the qualification will require all records be compared and of course the escalation should be run after hours. -----Original Message----- From: [EMAIL PROTECTED] To: arslist@ARSLIST.ORG Sent: Mon, 14 May 2007 3:39 PM Subject: Re: ITSM 7/LDAP not importing some records ** Thanks, Roger and Fred, I'll do that. Interesting that the Default value wouldn't be seen by Filters and Escalations. Have you found any other gotchas with LDAP? Also, am I assuming correctly that the Escalation, when it fires against the Vendor form, will do a fresh pull from LDAP vs. just getting whatever might be in that form from the last manual search? Rick _____ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG <javascript:parent.ComposeTo(> ] On Behalf Of Roger Justice Sent: Monday, May 14, 2007 12:09 PM To: arslist@ARSLIST.ORG <javascript:parent.ComposeTo(> Subject: Re: ITSM 7/LDAP not importing some records ** Yes, mine did the same thing and I created 2 escalations 1 if there was a phone number and 2 if there was no phone number. On the no phone number I hard coded the receptionist. -----Original Message----- From: [EMAIL PROTECTED] <javascript:parent.ComposeTo(> To: arslist@ARSLIST.ORG <javascript:parent.ComposeTo(> Sent: Mon, 14 May 2007 2:52 PM Subject: ITSM 7/LDAP not importing some records ** I have an ARDBC integration between ITSM 7.0.2 and LDAP that is working fine, except that it won't import records for which there is no phone #. Even though there is a Default Phone # in the Business Phone # field, only LDAP records with a value in the 'telephoneNumber' attribute get imported. The really puzzling part is that after running Filter and Escalation logs while the data is importing, the error is not generated from Remedy workflow, from what I can see. The Escalation displays that an error occurred at the end of each record's Push Fields, but is no more specific than that. The Filter logs don't show any related problems at all. Has anyone run into this before? Rick Cook __20060125_______________________This posting was submitted with HTML in it___ _____ AOL now offers free email to everyone. Find out more about what's free from AOL at <http://www.aol.com/?ncid=AOLAOF00020000000437> AOL.com. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"