Yes, I never tested this on Revit 2016. I will eventually.
Key Numbering in Excel does matter, but I forgot that I already fixed the limitation that I was referring to previously. My bad on that one. It used to matter more. However, yes now I am actually re-using automatically assigned numbers so if yours are out of order then they will only be used at the end to override the automatically assigned ones. In short, you are right - they don’t matter in your particular application.
TEXT only. That is correct. That was already mentioned on my post when I used big red squares to highlight parameter type.
Yes, numbers only and yes, it would be nice if they were whole numbers. Revit doesn’t particularly likes to use 2.1 as a Key Value.
You can use Extent input to constrain how much data gets read from Excel. It works just like Ranges in Excel ex. A1:C30 where A1 is origin and C30 is extent. That will ensure that anything in column D will not get transferred.
Thanks for great comments. I think I need to better handle Key Values so that they accept decimal places ex. 2.000 but not 2.100. Any ideas on how we can handle other parameter types? I am ok with just text, but I understand its quite limiting sometimes. Also 2016 support should not be too hard.