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
In this project, I have 2 forms (registration and monitoring), one dataset, and one submission to the monitoring form. The monitoring (update) submission is in the backlog because it was created offline and the registration (create) submission was not sent.
When I go to toggle the dataset to not require approval and reprocess all pending submissions, it shows this message indicating 1 submission that will be used to create an entity. This is misleading because this submission wont create an entity, even if force-processed, unless the dataset setting is changed before the force-processing occurs.
The messaging in this popup is from a time when we only had entity creates and is confusing and misleading now.
The "convert all pending submissions to entities now" functionality is also really hard to reason about now that we have offline entity updates and force processing. Does it still have a place? Could we consider removing it?
The text was updated successfully, but these errors were encountered:
In this project, I have 2 forms (registration and monitoring), one dataset, and one submission to the monitoring form. The monitoring (update) submission is in the backlog because it was created offline and the registration (create) submission was not sent.
https://staging.getodk.cloud/#/projects/133
When I go to toggle the dataset to not require approval and reprocess all pending submissions, it shows this message indicating 1 submission that will be used to create an entity. This is misleading because this submission wont create an entity, even if force-processed, unless the dataset setting is changed before the force-processing occurs.
The messaging in this popup is from a time when we only had entity creates and is confusing and misleading now.
The "convert all pending submissions to entities now" functionality is also really hard to reason about now that we have offline entity updates and force processing. Does it still have a place? Could we consider removing it?
The text was updated successfully, but these errors were encountered: