On Tue, 1 Jul 2025 21:00:56 +0200, Roland Gruber <p...@rolandgruber.de> wrote: >Am 30.06.25 um 19:05 schrieb Dave Hayes: >>> each module can provide wildcards and also defines where they can be >>> replaced (own + other module's). You can find it in the "wildcards" >>> section of the module's documentation, e.g. for Personal: >> >> Does this work for a group's custom field too? > >custom fields can consume wildcard values from other modules (in all >text fields). But they do not provide wildcard values themselves. > >The custom field type "Constant" allows additional wildcards based on >LDAP attribute values of all modules. See here for the complete list and >examples:
This did not work to set a group's "mail" field. I used %cn% and it was not replaced with the value of "cn". Instead I got: %c...@mydomain.com placed in the field before I save the actual record. I didn't actually try to save this record due to seeing this. My groups are of the form cn=<groupname>, cn=groups, (base DN) so perhaps your default to ambiguity is to not replace the token? -- Dave Hayes - Computer and Internet Consultant - LA CA, USA >> *Opinions expressed above are entirely my own* << You ask me what to do about your problems. It is my view that your real problem is that you are a member of the human race. Face that one first. _______________________________________________ Lam-public mailing list Lam-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lam-public
