There is no way to write to LDAP. The integration only is 1 direction.
Don......It's good idea to make it 2 direction with LDAP and Dynamic SQL .
1 of 1 people found this helpful
Now on version 12.1.08.001
I don't need to update LDAP, but rather the FP address book database. I just set up again from scratch and am still having the same issue.
1. Added a field to the Contact record type called 'Building' - this is not mapped to LDAP.
2. Verified that the newly created field 'building' was added to the FP address book database table.
3. Created a data link field in my ticket form to the FP address book table on the new 'building' field.
Now if I manually update the 'building' field directly on the database and then create a ticket, that value successfully pulls from the db to the ticket, so I know the link is working. Also, when saving the ticket, the associated contact successfully links to the ticket as expected.
The only issue is upon saving the ticket. The linked Contact is not updated from the ticket with a new value for 'building'. If a new ticket is opened for the same Contact, even though the 'building' was changed in a previous ticket, the new ticket still pulls in the old value because the Contact was never updated.
Am I missing something in the configuration or is this an issue with the application? Maybe I need an address book that is not linked to LDAP, and just run an import of users every once in a while?
From my experience and understanding from BMC, the address book you have is configured as an LDAP/AD address book; not a FP address book.That is the main issue you are having; since its considered an LDAP address book and its one direction only, you cannot write back into the address book - even if you have a field created there that is not 'mapped' to an AD attribute.
I think I understand what you're trying to do.. Basically have a field in your address book not tied to LDAP correct? I don't believe this is supported.