I know I’m late, but I was intrigued by the question
I guess it depends on what you want to do with the data. You could just add the sheet, and put the same value (from your one column) in both Name and Value columns. This would enable the robot to read it, and allow you to use the values. This does however mean that you would need to know the values by name in order to retrieve them during execution (dicConfig(“valuename”).tostring). This kind of defeats the purpose of the config file, because you are basically hard coding the values this way.
A better method (and I think maybe better fitting most scenarios?) would be to add the sheet (for example “ExtraSheet”) to the Excel file, add an extra array in_argument (in_extrasheets) to the settings workflow that contains the sheetname, and then read the file and loop through the sheets in in_extrasheets just like you do with the settings and constants. In the for each row logic, you could add items to a list that you then put in an out_argument.
This would result you in a list that contains all values that you can loop through without having to know the values in it.