@aaronrumple Thanks for the feedback.
I adjusted my code to be more in line with yours, and now it works, but I find that kind of weird.
Since I can’t seem to find the Schedule.GetCellText() in the API docs.
Also, the code that I used before, TableSectionData.GetCellText(), did the trick just fine with other code that we have in C#.
As I said, weird. But hey, the problem is solved, and it seems to work fine now.
I will try some further testing since I also need to know which parameters are adjustable and which are not. But as you said, that could be derived from the CellType, probably.
Is “Itemize every instance” unchecked in Sorting/Grouping?
That would do it. Those items would really be there - just grouped together. You can use the Count parameter on the schedule to see how many are in each group
I need to be able to cover both cases itemized and non-itemized schedules.
i’m thinking of introducing a parameter and drop the id’s in it and the temporaly adding it to the schedules to read them out and then roll back that transaction.
tha way it would just be a parameter read-out but it would use a lot of processing i fear and slow the scripts alot.
I’d just pull the method for grouping items from the schedule and then apply that to your own list of data. A list of lists. Python is very good at that sort of thing. And it is probably the fastest.
The parameters you need are already there because that is what the sorting and grouping is using…
For export you then just need the first item - item[0] - from each of the grouped lists. Everything in that group is the same. (…more or less. Some parameters may differ, but those aren’t parameters in the schedule.)