with the recent changes to Dynamo/Civil 3d, the script I once had working doesn’t seem to be working any longer, and I am not sure why. I am getting errors on the List.GetItemAtIndex nodes. I have attached an image of the error so as not to
There haven’t been any changes to the nodes in your graph. Have you confirmed that the data in the spreadsheet hasn’t changed? The script is doing a lot of lookups with hard-coded index values, so that could break pretty easily if the source data changes at all.
The index out of range error is because it is trying to get 573 items from a list that only has 532 things in it. In other words, this number doesn’t match with how many rows are in the spreadsheet.
The second issue is that it is pulling information from the second list (index 1) in the below screenshot, which is a bunch of nulls. This corresponds to column B in your spreadsheet, which is empty. You either need to adjust those indices, or delete Column B.
These are symptoms of what I mentioned above - hardcoding values like this makes for a very brittle script. I would recommend taking a look at this example, which demonstrates how to read the Excel data into a dictionary and then pull it out from there. This approach is much more resilient to changes in the spreadsheet. If you get it setup correctly, the only thing you have to worry about is that the column headers don’t change over time (“Survey Name” and “Roadway Name” in your specific case). But the columns can move around, the number of rows can change, and everything still works.