Maintain IDs for data received from CMS
Closed this issue · 2 comments
jacksos101 commented
For data received from the CMS (ie FactFiles, Tracks, etc), use the IDs supplied, rather than creating new ones.
This may require adjustments to be made on the CMS.
samuelgrant commented
This is especially important as the new API is likely to return APIs for almost everyting when users are looking for updates.
jacksos101 commented
Turns out that this wasn't actually the issue, and the app was maintaining IDs.