Re: ARDBC LDAP Vendor Form Question
It will be interesting to see what you find out from Support. This is one reason it is handy to have an LDAP browser <http://www.ldapbrowser.com/info_softerra-ldap-browser.htm>. Jason On Fri, Sep 26, 2014 at 7:21 AM, Arner, Todd wrote: > ** > > Thanks LJ! That worked. I also have a request open with support. I’ll > let you know if they have any solution to show all. > > > > Todd > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *LJ LongWing > *Sent:* Friday, September 26, 2014 9:10 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: ARDBC LDAP Vendor Form Question > > > > ** > > Todd, > > I have experienced the same, however, I have found that as long as I know > the attribute name I want, I can create the appropriate field, and in the > vendor field properties for that field, I just plug in the correct > 'attribute', and the values come across properly... > > > > On Fri, Sep 26, 2014 at 7:55 AM, Arner, Todd wrote: > > ** > > We are configuring the ARDBC LDAP to pull information from Active > Directory. We are trying to setup a vendor form to access the data and for > the most part this seems to be working. We are running into one issue that > I need some help figuring out. We create the vendor form by selecting the > ARSYS.ARDBC.LDAP vendor, and then select the appropriate table to see the > information we want. In this case we are selecting the entry associated > with the (objectclass=person). The issue is when trying to select the > attributes from the available columns, we only see some of the attributes. > Our question is why aren’t all the attributes included? > > > > This is all new to me so hopefully I’m making sense. I appreciate any > assistance you can provide. > > > > Thanks, > > Todd Arner > > > -- > > The information contained in this communication may be confidential, is > intended only for the use of the recipient(s) named above, and may be > protected under state or federal law. If the reader of this message is not > the intended recipient, you are hereby notified that any dissemination, > distribution, or copying of this communication, or any of its contents, is > strictly prohibited. If you have received this communication in error, > please forward the communication to no...@glhec.org immediately and > destroy or delete the original message and any copy of it from your > computer system. If you have any questions concerning this message, please > contact the sender. > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: ARDBC LDAP Vendor Form Question
Thanks LJ! That worked. I also have a request open with support. I’ll let you know if they have any solution to show all. Todd From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Friday, September 26, 2014 9:10 AM To: arslist@ARSLIST.ORG Subject: Re: ARDBC LDAP Vendor Form Question ** Todd, I have experienced the same, however, I have found that as long as I know the attribute name I want, I can create the appropriate field, and in the vendor field properties for that field, I just plug in the correct 'attribute', and the values come across properly... On Fri, Sep 26, 2014 at 7:55 AM, Arner, Todd mailto:tar...@glhec.org>> wrote: ** We are configuring the ARDBC LDAP to pull information from Active Directory. We are trying to setup a vendor form to access the data and for the most part this seems to be working. We are running into one issue that I need some help figuring out. We create the vendor form by selecting the ARSYS.ARDBC.LDAP vendor, and then select the appropriate table to see the information we want. In this case we are selecting the entry associated with the (objectclass=person). The issue is when trying to select the attributes from the available columns, we only see some of the attributes. Our question is why aren’t all the attributes included? This is all new to me so hopefully I’m making sense. I appreciate any assistance you can provide. Thanks, Todd Arner The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be protected under state or federal law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please forward the communication to no...@glhec.org<mailto:no...@glhec.org> immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: ARDBC LDAP Vendor Form Question
Todd, I have experienced the same, however, I have found that as long as I know the attribute name I want, I can create the appropriate field, and in the vendor field properties for that field, I just plug in the correct 'attribute', and the values come across properly... On Fri, Sep 26, 2014 at 7:55 AM, Arner, Todd wrote: > ** > > We are configuring the ARDBC LDAP to pull information from Active > Directory. We are trying to setup a vendor form to access the data and for > the most part this seems to be working. We are running into one issue that > I need some help figuring out. We create the vendor form by selecting the > ARSYS.ARDBC.LDAP vendor, and then select the appropriate table to see the > information we want. In this case we are selecting the entry associated > with the (objectclass=person). The issue is when trying to select the > attributes from the available columns, we only see some of the attributes. > Our question is why aren’t all the attributes included? > > > > This is all new to me so hopefully I’m making sense. I appreciate any > assistance you can provide. > > > > Thanks, > > Todd Arner > > > -- > The information contained in this communication may be confidential, is > intended only for the use of the recipient(s) named above, and may be > protected under state or federal law. If the reader of this message is not > the intended recipient, you are hereby notified that any dissemination, > distribution, or copying of this communication, or any of its contents, is > strictly prohibited. If you have received this communication in error, > please forward the communication to no...@glhec.org immediately and > destroy or delete the original message and any copy of it from your > computer system. If you have any questions concerning this message, please > contact the sender. > _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
ARDBC LDAP Vendor Form Question
We are configuring the ARDBC LDAP to pull information from Active Directory. We are trying to setup a vendor form to access the data and for the most part this seems to be working. We are running into one issue that I need some help figuring out. We create the vendor form by selecting the ARSYS.ARDBC.LDAP vendor, and then select the appropriate table to see the information we want. In this case we are selecting the entry associated with the (objectclass=person). The issue is when trying to select the attributes from the available columns, we only see some of the attributes. Our question is why aren't all the attributes included? This is all new to me so hopefully I'm making sense. I appreciate any assistance you can provide. Thanks, Todd Arner -- The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be protected under state or federal law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please forward the communication to no...@glhec.org immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
