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
It throws the following error at runtime using the noted CQL version:
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "HAPI-0389: Failed to call access method: org.opencds.cqf.cql.engine.exception.CqlException: Could not resolve call to operator 'ToString(java.lang.Class)' in library 'DQMFHIRHelpers'."
}
]
}
JP commented: Obviously we should catch that in the compiler.
Note this can't be reproduced using the current version of the VSCode Extension (v0.6.0) because the current VSCode Extension uses a prior version of CQL in which the above evaluates without error, i.e., doing the above works in the current VSCode Extension.
The text was updated successfully, but these errors were encountered:
I tested this with the latest version of clinical_quality_language and it seems that I'm able to go through the translation using this CQL test file
"library Test
using FHIR version '4.0.1'
include FHIRHelpers version '4.0.1'
context Patient
define function ToString(value id):
value.value"
The translation complete, no syntax error and I get my XML properly created after. Suggestion is to use the latest version of the translator to fix this issue.
The following is a bug that was working in a prior version of CQL, but does not work in the version of CQL used by https://releases.smilecdr.com/releases/2023/11/PRE/2023-11-PRE-35/:
It throws the following error at runtime using the noted CQL version:
JP commented: Obviously we should catch that in the compiler.
Note this can't be reproduced using the current version of the VSCode Extension (v0.6.0) because the current VSCode Extension uses a prior version of CQL in which the above evaluates without error, i.e., doing the above works in the current VSCode Extension.
The text was updated successfully, but these errors were encountered: