How to use Technical Officials id's in XLS templates

[hhagenes]

How to use Technical Officials id's in XLS templates ?
At first glance it looks like this is not currently possible, i.e. we want an id of ${session.referee1} and so on.
"technicalOfficials" : [ {
"level" : "National",
"iwfId" : "123456",
"federationId" : "78900",

[jflamy]

If you first create the technical officials

And then use them in the session assignments

Then the assignment report

Contains the assignments with the Ids.
This only works for the officials THAT MATCH EXACTLY the TO table.

[jflamy]

(using the dropdown guarantees that your assignments match the TO Table)

[jflamy]

So if you want the identification numbers or the level on the protocol sheet itself, no, this is not currently possible.
I would have to add a lookup function on the session to try to match the textual input back to the TO table. Which could be eventually be done. Something like ${session.jury1asTO.federationId} or something like that.

[jflamy]

One issue is that in large championships they have "self-registration" for referees. So they keep changing the TO assignments all the time, with new people coming in. For that purpose I was asked to allow updating the current TO sheet as the competition takes place (this is in version 57). So on one hand people want free-form, and other people need formal.

[hhagenes]

For the Norwegian federation all referees/officials has a unique id and currently I have to manually add the Id and level to the generated protocol for every session before importing it to the the national result database. Luckily there are less officials than lifters in a competition.

The toAssignments output/pivot table can be of help for us to automatically add the missing data in the protocol as a post step.

[jflamy]

You import the Excel protocols?

[hhagenes]

Example template
NVF stevneprotokoll-v6.xlsx
Yes, the organizer uploads the protocol to our results database after the competition and the data is not accepted if the NVF id and name do not match the results database.
Ideally each session should add a separate sheet to the output XL instead of one file pr session.

[jflamy]

I have added the capability in 57.0.0-alpha05
${session.referee1AsTO.federationId} -- the AsTO variation on the accessor retrieves the Technical Official object from the list of Technical Officials.

[jflamy]

In 57.0.0-alpha06 two more changes

• when importing a database export, the Technical Officials were not being read back. Now fixed.
• Added an "affiliation" field, that you can use to store the club (or whatever you need).