Update Timeseries and Location Group Stores to Support Partial Success

[msweier]

AI assisted feature request.

Is your feature request related to a problem? Please describe.
Groups are being used for a lot right now. Storing/patching a timeseries or location group is all-or-nothing: if 9 TSIDs are valid and 1 doesn't exist, the entire assign call fails and nothing is saved. PATCH may be worse the controller does rename -> unassign -> assign as separate non-transactional calls, so a failure on assign can leave the group renamed/cleared with no new assignments (related to #1654)?

Describe the solution you'd like
Support partial success on group assignment. AI suggests to add an ?ignore-missing=true query param to the TS group and location group store/patch endpoints. When set, CDA pre-validates the assignment list, sends only the valid entries to assign_ts_groups / assign_loc_groups, and returns 207 Multi-Status (or 200 with a body) listing the skipped IDs and reasons. Also wrap the PATCH controller's rename/unassign/assign sequence in a single transaction.

Describe alternatives you've considered
Right now, there is a lot of client side code being written to fall back or do a check if the locations/tsids are valid.

Chatbot suggests a better long term fix in the database. Add a DB-side variant (assign_ts_groups2 with p_ignore_missing and an OUT list of failed IDs) that wraps each iteration in its own BEGIN/EXCEPTION/END. Cleanest long term, but requires a cwms-database change and coordinated release.

Additional context
AI suggests the root cause — DB:

• cwms_ts.assign_ts_groups is a bare FOR loop with no exception handler, so the first bad TSID raises and rolls back the whole call.
• cwms_ts.assign_ts_group calls validate_ts_id / get_ts_code, which raise TS_ID_NOT_FOUND when the TSID is missing.
• cwms_loc.assign_loc_groups3 is a single MERGE, so it is atomically all-or-nothing in the same way.

CDA side:

• TimeSeriesGroupDao.assignTs — passes the entire TS_ALIAS_TAB_T array in one call.
• TimeSeriesGroupController.update — rename / unassign / assign run as separate DAO calls with no transaction boundary.
• LocationGroupDao.assignLocs and LocationGroupController.update — same pattern for locations.

[krowvin]

Potential overlap with

• [PATCH] TimeSeries Group does not update description #1607

Edit:

Clarifying that I said in my other post

Expect patch to update any fields provided and ignore any fields not presented.

Which I would argue is probably too vague. The issue title probably was resolved in that PR closed (1607)

[msweier]

To clarify why this is an issue, is districts are loading data into the dev database and some groups like aliases etc... have a lot of locations. I don't necessarily want all those locations in dev. When dev is smaller it performs faster in cwms-vue. Becomes tedious to weed out groups with locations/tsids that don't exist.

[MikeNeilson]

This doesn't seem unreasonable, but should probably be an optional "allow partial" failure or something like that.

[rma-psmorris]

When ignore missing is set, then this call should provide feedback on which assigned items were unable to be processed.