-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Silent failing of addAnnotations with "old" version of Hub Annotations #430
Comments
@tomwayson any thoughts on this :)? |
two approaches to consider / provide estimates @tomwayson
|
I'm looking into a migration script. In the mean time, a potential quick fix for this would be to see if the existing service has zero records, and if so, just remove it and call createAnnotationService(). |
I see you already did that. 🤦 |
FYI - this is the underlying issue regarding how the errors are swallowed: I think I'll have the rest-js functions throw an error if all records have an error. We could go a step further and have Let me know if you think the latter is necessary. |
@tomwayson thanks for the update. I think all having errors serves our purposes as an outdated schema will cause all of them to fail :) |
affects: @esri/hub-annotations ISSUES CLOSED: #430
affects: @esri/hub-annotations ISSUES CLOSED: #430
affects: @esri/hub-annotations ISSUES CLOSED: #430
@lisastaehli this has been released as |
We have received a bug report for Urban where a user was unable to add an annotation. We identified that the problem was that the ArcGIS Online organization of the user had an older version of the Hub Annotations layer where public annotations (Author = NULL) was not yet allowed by the schema (see error message below).
Of course there is an obvious workaround to this (probably) edge case: the user has deleted the old annotations layer (which was anyway empty) & added a new one with the current schema.
We would like to start a discussion on how to handle old versions of Hub Annotations layers with HubJS. In my opinion, there would be a few things that could be nice, e.g. notify the user if they are trying to connect to a feature service with an outdated schema and/or (automatically) migrate in this case.
Please note that we are currently still on version
2.2.4
of Hub JS. If this is handled in a newer version, please let me know :)The text was updated successfully, but these errors were encountered: