Hopefully a quick question, potential bug report:
Using CRUD Manager w/ autosync, if you load a data set with a cycle in it (any cycle), the cycle listener correctly fires and the resolution popup correctly shows.
But if you select a resolution in the popup and select "remove dependency" - it removes the dependency on the chart correctly, but that removal is not communicated back to the server; is not persisted. Reloading the page immediately with the exact same unchanged data results in another popup.
Similarly, if I set displaySchedulingIssueResolutionPopup
to false and manually remove a dependency from the store when the cycle
listener fires, the dependency is removed from the chart correctly, but I can't force the stores to communicate the removal back to the backend in any circumstances.
It seems like the cycle resolution happens and treats that post-resolution state as the clean initial state with no changes to sync/save.
Is this expected behavior? I feel like it should not be, as a change needs to be communicated to the backend for persistence. Is there any way to actually communicate the change back to the server?