You likely have some base set of licenses installed on all your controllers, and some controllers may have additional licenses. You could configure your script in such a way that you import the base, then do a license check before importing optional settings:
I found out why the options were not importing properly. I had some extra white space after the option in the csv. I did not notice it at first because I was using EXCEL to view the file, but when I opened it in wordpad I was able to clearly see it. I corrected these and then I was able to import.
Re: What would YOU like to see in the Data ONTAP PowerShell Toolkit?