Jump to content

LDAP Timestamp to Date & Time Conversion in reporting.


QEHNick
 Share

Recommended Posts

Good afternoon.

I am attempting to run a report to determine if an active directory account is about to expire based on a custom attribute which is imported from the accountExpires attribute.

The problem is, the "LDAP Timestamp to Date & Time" conversion produces a date which is backwards (2022-06-03 00:00:00 for example).

This makes it impossible to report on in any automatic way using the built in reporting variables ({{DATE:startofweek}} AND {{DATE:endofweek}} etc.)

Is my only option to "freehand" it in the SQL Schema Designer and MacGyver some conversion of the date there?

Link to comment
Share on other sites

What Custom Attribute (in what table) are you storing it in?

That is the standard format for a DateTime - for example if you filter on Date Logged against {{DATE:startofweek}} this works fine and that is stored in the same format.

It may simply be that you need to store it in a DateTime field.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...