Hi, I look at this answer and it for an old version. How can this be done with the current version?
Best regards Kristoffer
Hello Kristoffer,
Have a look at the following help article: https://www.adaxes.com/help/PropertyForDisplayNames.
Adaxes, the tool that just keep on giving! Thanks for the guidance.
We have a preoperty pattern for accepted Country names which has a list of codes. For our case country code VM which "Vietnam" and I believe based on some google research "Viet Nam" is also correct.
When the UPN being created is the same as an existing one except for the case. For instance, the new UPN is sally.fields but there's an existing Sally.Fields. The ... but then fails to create the AD account indicating that the UPN is not unique forestwide.
Can you point me to documentation to upgrade from Adaxes 2019.2 ver 3.1.2.174230 to the current version please?
We are upgrading some of our applications from dotnet framework to dotnet 6+ and we have found that the Adaxes SDK is not compatible. When can we expect compatibility? Thanks
Can you clarify the answer as it's a bit confusing? Will there be new major release available this month?