You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something that must've been an oversight when I added support for it but only noticed now, if you import a schedule with an "external ID" set, we never attempt to keep the internal IDs for the teams/players even if they are identical. Some logic could be added to keep any IDs the same if the external ID for that run matches,
From my limited testing, this may also happens when you simply edit a run too?
The text was updated successfully, but these errors were encountered:
zoton2
changed the title
Attempt to keep same team/player IDs when importing schedules
Attempt to keep same team/player IDs when importing schedules/editing runs
Feb 25, 2021
As an extension of this, adding an externalID to both teams and players should help this. Horaro would just have to be a hash based on information we have (similar to what I do already for the runs themselves if no external ID is found) although Oengus does have IDs that can be used for players at least.
zoton2
changed the title
Attempt to keep same team/player IDs when importing schedules/editing runs
Attempt to keep same team/player IDs when importing schedules/editing runs, add external Ids
Mar 4, 2021
zoton2
changed the title
Attempt to keep same team/player IDs when importing schedules/editing runs, add external Ids
Attempt to keep same team/player IDs when importing schedules/editing runs, add external IDs
Mar 4, 2021
Something that must've been an oversight when I added support for it but only noticed now, if you import a schedule with an "external ID" set, we never attempt to keep the internal IDs for the teams/players even if they are identical. Some logic could be added to keep any IDs the same if the external ID for that run matches,
From my limited testing, this may also happens when you simply edit a run too?
The text was updated successfully, but these errors were encountered: