NextGen (Mirth) Connect 3.11.0 Released!

NextGen (Mirth) Connect 3.11.0 is now available as an appliance update and on our GitHub page. This release contains improvements to licensing and the NCPDP data type. It also includes various security fixes, general bug fixes, and improvements to commercial extensions. See the release notes for the complete list of fixes and improvements.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

on-update statement problem

  • Filter
  • Time
  • Show
Clear All
new posts

  • on-update statement problem


    I have a channel with a database connection in the source side.

    I want to use 'Run on-update statement' event in order to mark every record sent.

    I've created a new table called TRU_INTTB001 where I intend to save the records sent identifier because I can't add a status field in the master table.

    The 'on-update SQL' field contains:
    INSERT IGNORE INTO TRU_INTTB001 VALUES (${historia},${epi},SYSDATE,'UCI001');

    When I deploy and start the channel it seems work fine (no errors, and messages sent well) but nothing happens in TRU_INTTB001 table. There are no records in.

    The database user have correct permissions to write in this table.

    Anybody knows why?

    Thanks a lot.

    carles massalle
    uci01x.xml (25726 bytes)

  • #2
    Ren-update statement problem

    What does the XML look like that the DB reader generates for a new row?
    Chris Lang


    • #3
      Ren-update statement problem

      sorry, the xml attached file is the channel export.

      I believed that the "on-update" event in dbreader could make INSERTs, UPDATEs or DELETES on tables on database source when the message was sent.

      it isn't correct?