Clovertech

Files are read in wrong order by Fileset-local Inb. Thread

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Files are read in wrong order by Fileset-local Inb. Thread

  • Creator
    Topic
  • January 30, 2018 at 5:53 pm #55600
    Linus Betschart
    Participant

      Hi all

      We use Cloverleaf 6.1.1.0P

      We see that on file-based inbound communication (Fileset-local, order set either to TimeStamp or Alpha), it does not always read the files in the correct order.

      This results in wrong results in our destination system.

      In the example pictures you see in green the order how Cloverleaf read the messages, in purple the order we expected them to be read. In x02.png you see that it read file …163.hl7 before …161.hl7.

      Anybody can help?

    • Creator
      Topic
    Viewing 5 reply threads
    • Author
      Replies
      • January 30, 2018 at 7:16 pm #85873
        Michael Hertel
        Participant

          It looks like you are showing the smat database sorted by time or something like that.

          If you notice the message id’s are in order, it’s just that the display is not in order, so you should be good.

        • January 31, 2018 at 8:41 am #85874
          Linus Betschart
          Participant

            Michael Hertel wrote:

            If you notice the message id’s are in order, it’s just that the display is not in order, so you should be good.

            I need to disagree. The message id’s on the left are align with the time stamp. That’s all… But they are not align with the FileName order.

            File ..542.hl7 should be read before File …543.hl7. But this is not the case!

          • January 31, 2018 at 1:01 pm #85875
            Michael Hertel
            Participant

              You are correct, x01.png looks wrong.

              I was looking at x02.png. Which if you put in order by message id still looks correct to me. The timestamp is the same for the files.

              Anyway, x01.png looks wrong.

            • January 31, 2018 at 4:56 pm #85876
              Linus Betschart
              Participant

                Implementing the tps_fileset_dir_pars script mentioned in this post seems to have solved the issue:

                Directory Parse TPS

                Nevertheless, I do not understand that this is necessary ❓

              • January 31, 2018 at 5:02 pm #85877
                Michael Hertel
                Participant

                  This isn’t the first time an option seems to be there more for decorative purposes than function.

                  I would suggest opening a ticket with Infor pointing out that the check box option is not working as expected.

                  If they fix it, you’ll save us all a lot of grief in the future when we tangle with this issue.

                  😀

                  BTW, I’m not seeing the post you are referencing to with the parse script.

                • February 1, 2018 at 7:40 am #85878
                  Linus Betschart
                  Participant

                    Michael Hertel wrote:

                    BTW, I’m not seeing the post you are referencing to with the parse script.

                    it is the very first post which contains tps_fileset_dir_parse

                • Author
                  Replies
                Viewing 5 reply threads
                • The forum ‘Cloverleaf’ is closed to new topics and replies.