Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Database reader source XML tags casing is no longer all lowercase in 3.12.0 #5083

Closed
pladesma opened this issue Mar 7, 2022 · 0 comments
Labels
bug Something isn't working Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-7366 triaged
Milestone

Comments

@pladesma
Copy link
Collaborator

pladesma commented Mar 7, 2022

Describe the bug
Using the Database Reader, the generated XML message used to always convert the result tags to lowercase. But in 3.12.0, it instead follows the casing that was provided by the SELECT statement.

To Reproduce

  1. In a Database Reader, use Mirth Connect to generate a SELECT statement such as:
    SELECT MYTABLE.TESTID AS TESTID FROM MYTABLE
  2. Then in the source transformer, let Mirth generate an inbound message template.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <result>
 <testid>value</testid>
 </result>
  1. Use a message builder step to generate the following JS code
    tmp['row']['column1'] = validate(msg['testid'].toString(), '', new Array());
  2. Deploy the channel. A message such as the following will be received:
<result>
 <TESTID>6221715</TESTID>
 </result>

Expected behavior
The resulting XML message should have lowercase tags.

Actual behavior
The resulting XML message follows the casing from the SELECT statement.

Environment (please complete the following information):

  • OS: Linux
  • Java 8
  • Connect 3.12.0

Workaround(s)
Change the aliases in the SELECT statement to be all lowercase, i.e. SELECT MYTABLE.TESTID AS testid FROM MYTABLE

Additional Context
Relates to #4878

@pladesma pladesma added bug Something isn't working Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker triaged RS-7366 labels Mar 7, 2022
@pladesma pladesma added this to the 4.0.0 milestone Mar 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-7366 triaged
Projects
None yet
Development

No branches or pull requests

1 participant