ralized time?
Thanks and regards,
Colin
-Ursprüngliche Nachricht-
Von: Roland Gruber
Gesendet: Samstag, 24. Juni 2023 20:20
An: lam-public@lists.sourceforge.net
Betreff: Re: [Lam-public] Custom Field Type LDAP Date not mapping correctly to
Windows Active Directory Generalized Time fiel
rds,
Colin
-Ursprüngliche Nachricht-
Von: Roland Gruber
Gesendet: Samstag, 24. Juni 2023 20:20
An: lam-public@lists.sourceforge.net
Betreff: Re: [Lam-public] Custom Field Type LDAP Date not mapping correctly to
Windows Active Directory Generalized Time field
Hi Colin,
I think this
Hi Colin,
I think this is because AD uses a different date format.
LAM expects "1994041300Z" while you need "1994041300.0Z".
The solution would be to use a text field with date type validation. But
looks like the "Z" is causing issues. Will dig deeper and provide
feedback the next few
Hello Roland,
We recently set up LAM Pro with Active Directory for managing our theatre
internal user accounts.
In general it works fine, now Im about to add some custom attributes to AD
and map them in LAM accordingly.
Where Im having trouble is with LDAP date type custom fields.
I
