How to disable renaming of custom schema on VSCode import?

Question

Question

during an upgrade, a customer wants to load custom schemas in a particular order.
For this, they renamed a file EPIC_MDM.HL7 to 1EPIC_MDM.HL7
Upon importing this file into their server using VSCode, the custom schema was renamed to 1EPIC_MDM.HL7 inside the <Category>

This is impacting the upgrade and they are looking for a way to import a custom schema without renaming the schema itself.

Product version: IRIS 2024.1

$ZV: IRIS for UNIX (Red Hat Enterprise Linux 7 for x86-64) 2022.1 (Build 209U) Tue May 31 2022 12:13:58 EDT [HealthConnect:3.5.0] [HealthConnect:3.5.0]

Discussion (2)2

Log in or sign up to continue

Brett Saviano · Aug 26

Hi @Gramen Tontchev, for non-classes and routines on the local file system the main extension needs to use the file name to determine the name of the document on the server. There's no guarantee that all "other" document types will have the name of the document stored in the text, and even if that were true, it would be very difficult for the extension to know how to extract that info from each one. I have a PR open that will improve the client-side editing workflow, but this behavior remains the same.

TL;DR: The name of the file must match the name of the document on the server.

0 0

score 0 · Answer 1 · 2024-09-10T10:12:01-04:00

Thank you, Brett. I will inform the customer. We decided to rename the file to match the document on the server.