Information about the election itself is currently included in the last row of data with the last elected scout, but not in the rows with additional scouts that were elected, which means whole-election-relevant data such as the chapter name, troop number, and election date needs to be manually copied to the additional records before it can be imported into the Lodge Management software (OA LodgeMaster in this case).
There are also race-condition problems here because if two people enter two separate elections at the same time, their information gets mixed together as each scout row is added to the table as it gets entered, regardless if the "last scout elected" row has been submitted yet.
This information should be collected and stored separately, and then combined with each scout record as part of the CSV data export process.
Information about the election itself is currently included in the last row of data with the last elected scout, but not in the rows with additional scouts that were elected, which means whole-election-relevant data such as the chapter name, troop number, and election date needs to be manually copied to the additional records before it can be imported into the Lodge Management software (OA LodgeMaster in this case).
There are also race-condition problems here because if two people enter two separate elections at the same time, their information gets mixed together as each scout row is added to the table as it gets entered, regardless if the "last scout elected" row has been submitted yet.
This information should be collected and stored separately, and then combined with each scout record as part of the CSV data export process.