fix: DTOSS-11698 updated the shared data service handler so DELETE works with GUID keys #1776
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Description
Introduce robust key conversion for data service Delete/GetById/Put operations so GUID primary keys are handled correctly.
RequestHandler.CreateGetByKeyExpression(...)to:ConvertKeyString(...)helper.Guid,Enum,DateTime, andstring; fall back toConvert.ChangeTypewith invariant culture.using System.Globalization;for invariant conversions.File changed:
application/CohortManager/src/Functions/Shared/DataServices.Core/RequestHandler.csContext
After the ServiceNow cases table switched to a GUID primary key (
Id), Playwright cleanup started failing on DELETE. The generic handler usedConvert.ChangeTypefor key conversion, which does not supportGuid, causing DELETE to return non‑2xx andexpect(deleteResponse.ok()).toBeTruthy()to fail. This change parses GUIDs properly, restoring DELETE behavior forServiceNowCasesDataServiceand any other data service that may use GUID keys in future.Supports the change in https://nhsd-jira.digital.nhs.uk/browse/DTOSS-11698
Type of changes
Checklist
CreateGetByKeyExpressionwith a GUID key as a follow-up.Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.