masseyfHi,
We're trying to search using the Advanced Search feature of the dashboard. What we'd like to do is search for all product keys that have had, for example, more than 2 activations performed. We tried a search on Total Activations but the result is always ALL the product keys. We assumed that "Total Activations" refers to a counter that increments by one each time an activation is performed. If not, what's the use of "Total Activations"?
We tried the obvious "Number of activations" "More than" "2" "Total Activations" then tried variations but the results are always all product keys.
Thanks.
masseyfHmm. To answer my own question: "Total Activations" refers to the number of times a product key can be activated, not the number of times activations have been performed using a product key.
Please correct me if I'm wrong.
The number of times activations have been performed would be a great info to have and something we should be able to limit in a time span.
What you're looking for is "Used activations" -- meaning the number of activation slots that has been used for the product key.
"Total activations" means the total available activations (used or unused) for the product key.
But I can see how this can be confusing, we'll clean this up and make it easier to understand.
masseyfActually, what we were looking for was the number of times a product key has been activated in total. We think some users are sharing the software (installed on more than one computer), and the software is activated then deactivated, reactivated on another computer then deactivated, so on and so forth. We'd like to know how many times that has occured.
Hmmm... that's an interesting use-case. Right now, the only way to get that information is to use the "Account activity" page in your LimeLM dashboard (or the corresponding web API function). But that doesn't let you filter by "uses", only by date. So if you set the date range to be a month, you can easily visually see which keys are being deactivated / activated frequently (they'll have a huge list of activations / deactivations).
Though I can see the benefit of what you want to do. We'll think about the best way to add something like what you're looking for.
masseyfIf such a "counter" would exist, it would extremely usefull to be able to limit it. So, for example, limit the number of "activation-deactivation" cycles to say, 5, during the year/month (or other time frame) following original activation.
You're right this is useful. We'll run through some design ideas and think about adding it.
