Community
    • Categories
    • Recent
    • Popular
    • Users
    • Search
    • Register
    • Login

    UserID data inconsistency - new Mandants

    Scheduled Pinned Locked Moved Development
    5 Posts 2 Posters 3.9k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      jannav
      last edited by

      Dear I-Doit team,

      we have data inconsistency in tables isys_person_intern across all Mandants. By inconsistency i mean that userX has in first mandant id 44 and id 25 in second Mandant. This becomes problem in case user wants to swicht mandant using drop-down menu (left top corner of I-Doit interface) and becomes following error:

      
      isys_exception_database : Query error: 'UPDATE isys_user_session SET isys_user_session__isys_person_intern__id ='44' WHERE isys_user_session__php_sid='ca6a46ae4afbd436f5944cc6d06f9ef9';': Cannot add or update a child row: a foreign key constraint fails (`idoitnew_mandant2/isys_user_session`, CONSTRAINT `isys_user_session_ibfk_1` FOREIGN KEY (`isys_user_session__isys_person_intern__id`) REFERENCES `isys_person_intern` (`isys_person_intern__id`) O) :CMDB > Server > rvimsapps > Übersichtsseite
      Logged in as: userx
      
      

      Idoit version: 0.9.9-1

      My guess is that inconsistency begins once you work just with one Mandant for some time (and users are created in mandant1 schema) and then you create second mandant. Users will login into system and they are created in mandant2.isys_person_intern under different IDs (depends in which order they login for the first time after second mandant was created) than it is in first schema (mandant1).

      Can you please have a look on this bug?

      1 Reply Last reply Reply Quote 0
      • dsD Offline
        ds
        last edited by

        Hmm, what about updating i-doit to 0.9.9-6 first? 🙂

        1 Reply Last reply Reply Quote 0
        • J Offline
          jannav
          last edited by

          does it mean that you know about the issue and it has been fixed in 0.9.9.6 or that you don't support older than current versions?

          1 Reply Last reply Reply Quote 0
          • dsD Offline
            ds
            last edited by

            Yes it is fixed

            1 Reply Last reply Reply Quote 0
            • J Offline
              jannav
              last edited by

              thank you

              1 Reply Last reply Reply Quote 0
              • First post
                Last post