Re: Current LDAP Limitations?

2010-05-12 Thread Jason Miller
> As for #2 I believe it is a setting in the AD for max rows returned. > > Fred > > -Original Message- > From: Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] On Behalf Of William Rentfrow > Sent: Wednesday, May 12, 2010 12:06 PM > To:

Re: Current LDAP Limitations?

2010-05-12 Thread Scott Hammons
Sent: Wednesday, May 12, 2010 2:49 PM To: arslist@ARSLIST.ORG Subject: Re: Current LDAP Limitations? I am currently using ARS 7.1.0 Patch 007 (on Solaris). I can see the Date/Time fields on my vendor form but still cannot query by them. Anybody on 7.5 want to add whenChanged or modifyTimeStamp to

Re: Current LDAP Limitations?

2010-05-12 Thread Grooms, Frederick W
for max rows returned. Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of William Rentfrow Sent: Wednesday, May 12, 2010 12:06 PM To: arslist@ARSLIST.ORG Subject: Current LDAP Limitations? ** Back around Remedy 5.6 was

Re: Current LDAP Limitations?

2010-05-12 Thread Andrey
2010/5/12 William Rentfrow : > ** > Back around Remedy 5.6 was the last time I tried to pull large quantities of > data from Active Directory using the Remedy LDAP/ARDBC > Active Directory > integration. > > Setting it up was easy but we had two issues back then: > > 1.) We couldn't query by date f

Current LDAP Limitations?

2010-05-12 Thread William Rentfrow
Back around Remedy 5.6 was the last time I tried to pull large quantities of data from Active Directory using the Remedy LDAP/ARDBC > Active Directory integration. Setting it up was easy but we had two issues back then: 1.) We couldn't query by date fields - no results were returned 2.) Page si