Stream: IG creation
Topic: new error with publisher update
Brian Reinhold (Mar 11 2021 at 11:22):
I just updated the publisher to the latest version and got this new error which I don't understand:
StructureDefinition/PhdBitsEnumerationObservation: StructureDefinition.snapshot.element[27].fixed.ofType(uri) error
The element Observation.extension.url has a fixed of type uri, which is not in the list of allowed types ([http://hl7.org/fhirpath/System.String])
It seems very basic ... all my structure definitions have it in the element location 26 or 27 (however, I don't know how to locate element 26 or 27 as I don't know what the validator counts as an element and where element 1 starts). Anyone understand this new error?
Jose Costa Teixeira (Mar 11 2021 at 11:43):
Brian Reinhold (Mar 11 2021 at 12:37):
Jose Costa Teixeira said:
Its a start, but I don't know WHY my fixed uris (all defined FHIR urls) would be illiegal. My version is also 4.0.1 though it still works with the current build (functionally).
Chris Moesel (Mar 11 2021 at 13:13):
@Brian Reinhold -- right. I think the discussion on that other thread implies it is an issue with the IG Publisher. Your fixed uris are likely LEGAL -- the IG Publisher is just spitting out false errors. At least that seems to be the consensus.
Brian Reinhold (Mar 11 2021 at 13:32):
@Chris Moesel
Guess what, I changed <fixedUri> to <fixeduri> and the error went away...
BUT only in one place, an extension. I have <fixedUri> in many other places and they produce no error. I am going to assume that it is a bug introduced with the update given its inconsistency.
Chris Moesel (Mar 11 2021 at 13:35):
That is really weird! Just be careful if you actually commit that change (fixeduri) -- because once they fix the bug, that may get flagged as an error after that (an in that case, it would actually be a valid error).
Brian Reinhold (Mar 11 2021 at 13:36):
I am not going to make that local 'fix'. I am changing it back and putting it in the ignorewarnings file
Lloyd McKenzie (Mar 11 2021 at 15:41):
If it's an error, you can't suppress it with ignorewarnings. @Grahame Grieve @Mark Iantorno
Brian Reinhold (Mar 11 2021 at 19:08):
@Lloyd McKenzie I put it in the ignorewarnings.txt but it did not suppress the error. So I have found out.
Last updated: Apr 12 2022 at 19:14 UTC
