Our team, Autodesk Developer Network / Forge Partner Development, created a few add-in's for the Autodesk App Store, including the Fusion 360 one as well (they all have the support email: firstname.lastname@example.org)
The main purpose of those add-in's were to show how powerful API's can be, how it can help you automate boring tasks, e.g. moving parameter values from Fusion 360 to another application and back. When you select these add-in's in the Scripts and Add-Ins dialog of Fusion 360, then you can click "Edit" and see the source code. You are free to use that source code, modify it, and even use it to create a commercial app out of it :)
If you think that some of the functionality shown by those add-in's should be part of Fusion 360, then you can ask for that on the Fusion 360 IdeaStation :)
After that small intro, here are the two errors that people contacted me about so far concerning the Parameter I/O add-in. I have not heard of other ones yet:
1) Cannot import CSV file after editing it in Excel
Maybe other apps could have this issue too, but I've only heard of Excel in this context. Parameter I/O expects the CSV file's content in a given format. In each line of the file there should be values formatted like this: <parameter name>,<unit>,<value>,<comment>
Please note that each value is separated by a comma, just like the meaning of CSV suggests: CSV = Comma Separated Values. Any of the values could also be wrapped in quotation marks as well: "MyParam",in,"12.00","Some comment"
Depending on your computer's Regional or Locale settings, Excel might use another character (e.g. semi-colon ';') to separate the values. Parameter I/O does not like that :(
So please open up the problem CSV file in a Text editor and make sure that the formatting is correct before trying to import the values from it. You can also find articles on the net about changing the character Excel is using for value separation.
2) Cannot move parameters from one model to another
In other words, the workflow in question is: export parameters of one model, then import it in another model.
You might run into issues when in your model one parameter is referencing another one, e.g. MyParam1 = MyParam2 * 3
When you export the parameter values from your model, they might be saved in the CSV file in a way that a parameter is being referenced before it's declared:
Unfortunately, if you leave the CSV file like that and try to import it into a new model which does not have those parameters yet, then the program will throw an error during the import. That's because when creating MyParam1, the program is trying to set its value to something that does not make sense at that given moment: MyParam2*3
The problem with that is that MyParam2 does not exist in the new model just yet.
You would have to reorganize the content of the CSV file in a way that MyParam2 is declared before MyParam1.