Managing 250 licenses with multiple feature keys

Good Morning,

So, next version of product, and even more use of feature keys (very neat remote "control").

Three questions if possible please:

1. Export / alter / Import (overwrite)

Can we export all our (existing) product keys, alter the data (add more columns of feature keys, fill in Excel etc. and create on LimeLM) and then import *overwriting* (or rather editing/amending) existing users?

2. Default value for a feature

We're adding new features which we'd like to default to "on" (checkbox = 1); as adding a "negative feature" (check to turn off) seems to be likely to trip us up in the future..

Can't see how to set default - can it be set (on a per-feature key basis)?

3. Alter our Feature key "types"

When we set up feature keys we used strings (is checkbox relatively new?) - so "yes" or "true" for on...

Now it'd be much nicer if we could use checkboxes - that means altering our existing data...

Can we do that somehow? (maybe #1: i.e. export, alter [incl. delete/add feature keys with different data type] then (re) import?)

Thanks!

Dr. Michael Dye.

Can we export all our (existing) product keys, alter the data (add more columns of feature keys, fill in Excel etc. and create on LimeLM) and then import *overwriting* (or rather editing/amending) existing users?

No, you have to modify the keys in LimeLM either using the LimeLM UI or using the web API.

You could benefit from using the bulk editing in LimeLM. just select multiple keys and click "Edit".

Can't see how to set default - can it be set (on a per-feature key basis)?

It's coming.

Can we do that somehow? (maybe #1: i.e. export, alter [incl. delete/add feature keys with different data type] then (re) import?)

Add a new custom license field of the type you want, loop through all the keys and set that new custom license field to whatever you want, delete the old field, rename the new field.

Thanks Sam; we've done (doing) a little Windows program that uses the API to download the license data; present it in a grid with column header checkboxes and all that sort of stuff; and then upload changes (it can also export/import Excel so gives us that ability too). So far so good...

I don't understand why you don't just alter the data inside LimeLM? Is the multi-key editing confusing?

Thanks Wyatt,

Well; firstly we started on our little Windows app before we read Sam's reply 🙂

Secondly we often find it difficult to select the "right" product keys - as we tend to forget the email address associated with them... So selecting multiple for editing won't be straightforward.

Third we've added three "feature keys" that are just strings: User name, Company and Country. Not read by the app but great for finding/sorting/grouping/filtering (and remembering who has the key!).

So we download the data into a grid in a WinForms app (Janus grid); and bingo we've got sort, filter, group etc. Then we can check/uncheck loads of data in one header click. We can also store this for reference and added the ability to import/update a load of users from CSV (so set up the various columns, or overwrite etc.).

And lastly; when we started our feature keys we didn't spot (was it there?) "checkbox" type so we had a string and allowed (parsed) yes, no, true, false, on, off - so people could get away with typing different things in to enable license features. We never parsed "1", "0": so unfortunately if we replace any feature key with a checkbox the LimeLM web would be easier to use but existing versions of the app would get all upset!

Hope that explains it!

(Now I'll go and take a look at multi-key editing...)

We've added support for default values for custom license fields (inside LimeLM in the web API). We'll be updating the custom license fields documentation shortly so that it will highlight this added functionality.

Reply
Discard post