Thanks Wyatt, I figured it would be something along those lines. If I have the default value for the created field set to the creation time, can I leverage that when updating field values using the above? i.e. can I just call a set value, providing the feature name only (and no value), or do I then need to do a get details for each individual key that I have returned in order to get this value?
Back filling new "created" feature valueAnswered
Hi Wyatt, I hope you are well.
I've belatedly come to the conclusion that I need a "created date" field in my keys that I can access from within my application, to limit features/show eligibility for free upgrade etc.
I've been playing around in a product within LimeLM and have added a created field that defaults to the key creation time (no problems there), but what I really want to do is back fill this feature value for all of my existing keys. Could you point me in the right direction please?
thanks,
Matt
Answer
Hey Matt,
The best way to handle this (since every pkey will have a different value) is to loop of chunks of pkeys using the web API, then set the field for those pkeys.
Advanced search will include the created field that you can then use to set the custom license fields.
So, search for pkeys where that field is empty, then set if for those pkeys.