I believe right now, it will be the order in which you add activities to your operation. Last one wins.
We might want to figure out a better way? It’s tricky because some might want to ensure POTA is there, even if there’s a MY_POTA_REF, because they care most about POTA and their other logging apps don’t know about the newer MY_POTA_REF fields.
Others might want the opposite, since POTA, WWFF and SOTA have their own fields, use SIG for other activities.
@KI2D It’s actually a little more interesting that this.
Multi activation… First in the list comes first EXCEPT when you do a Park2Park and do not record the park number of that first program.
So e.g. POTA then WWFF.
Select spot for Park2Park which contains only the WWFF reference.
Export is then SIG=POTA, but for QSOs with P2P WWFF and no POTA equivalent installed, SIG becomes WWFF and POTA is ignored.
It’s interesting and I actually like it.
Bottom line POTA does not require any SIG_INFOs recorded at all to get that credit. Whereas WWFF requires at least one station to record the SIG_INFO.
So going thru the log and making sure all POTA SIG_INFOs are correct is unnecessary. And picking up the WWFF is fine. Odds are, you will not miss any P2P credit in either program.
The current export methods of separate logs with no details for submission, plus the full which still contains all lookup details as they come thru are reducing my post activation workflow considerably.