Skip to main content

Getting all deltas from Auth0

Before I get in to the solution of this article, let me tell you how it started and fill you in on the problem that arose.  I wrote a procedure to get daily deltas of users - those of which who had created/updated their account on the given day (and including the day before for good measure on the GMT timestamp).  The simple search criteria was just the following:

updated_at:[yyyy-mm-dd TO yyyy-mm-dd]

Simple, right?  the []'s being the dates are inclusive, while using {} would mean exclusively.  Auth0 lets you mix these on either side depending on your use.  While this is all well and good, Auth0 will limit the number of results (even with paging) to 1000 only.

So, your first option is that you could have your procedure create a user export job, and then parsing through the results and eliminating those which do not meet your updated_at search criteria.  I can tell you first hand that eventually the amount of users will just get to be too much and cumbersome to process through.  However, I've been told by the good people at Auth0 that currently in their development pipelines, they are making an update to this procedure where you can use search parameters.  More on that later.

Otherwise, I have come up with the following:

* One thing to note on the above script is that on line 9, set page to 0, not 1.  

This creates a recursive promise, and running through the pagination for as much as it gives it.  For every 1000th record it comes to, it takes the created_at date from the last user, and concatenates on to the end of the query:

created_at:{yyyy-mm-ddThh:mm:ss.nnnZ TO *]

This makes it go from this date/time (exclusively) to the max it can find.  Important to note here as well that results from every query are being sorted from the created_at field in ascending order.  Which means it's going to start from the earliest first.

As always, hope this helps.  I sure wish I knew this in its entirety before I started, frustrating having to make amends and re-query past days in order to catch up.

J.

Comments

Popular posts from this blog

Running NodeJS Serverless Locally

 So it's been a long time, but I thought this was a neat little trick so I thought I'd share it with the world - as little followers as I have.  In my spare time I've been writing up a new hobby project in Serverless , and while I do maintain a staging and production environment in AWS, it means I need to do a deployment every time I want to test all of the API's I've drafted for it. Not wanting to disturb the yaml configuration for running it locally, I've come up with a simple outline of a server which continues to use the same configuration.  Take the express driven server I first define here: And then put a index.js  in your routes folder to contain this code: Voila! This will take the request from your localhost and interpret the path against your serverless.yml and run the configured function.  Hope this helps someone!

question2answer Wordpress Integration

 Today I want to journal my implementation of a WordPress site with the package of "question2answer".  It comes as self-promoted as being able to integrate with WordPress "out of the box".  I'm going to vent a small amount of frustration here, because the only integration going on is the simplicity of configuration with using the same database, along with the user authentication of WordPress.  Otherwise they run as two separate sites/themes. This will not do. So let's get to some context.  I have a new hobby project in mind which requires a open source stack-overflow clone.  Enter question2answer .  Now I don't want to come across as completely ungrateful, this package - while old, ticks all the boxes and looks like it was well maintained, but I need every  page to look the same to have a seamless integration.  So, let's go through this step by step. Forum Index Update This step probably  doesn't need to be done, but I just wanted to mak...

Google Sheets Web App

 Greetings! Has been yet another long period since my last post, but hopefully the type of content makes up for it.  Today I'm writing about a need that I had to document my entire movie collection in Google Sheets, because some that were on my local network, some on DVD, some on my Playstation Video account and as well as my small collection in Google TV.  All in all there is currently over 500 movies, and growing. So the spreadsheet is fine on its own, but something nice and "pretty" was needed to list, search and filter by the movie's attributes.  I first got an API key to be used with  OMDB API .  This allows me to get a JSON of the movie's IMDB attributes with a search from the title.  I then added two functions in the "Apps Script" component of the sheet: From here, I could call the function to search (from a cell) with: =API(CONCAT("http://www.omdbapi.com/?apikey=*******&t=",ENCODEURL(A1))) That would return the JSON (assuming A1 is...