3

Warning of dynamic multi choice bug

Hi all -

I reported an issue to Ninox where the data in a dynamic multi choice (dMC) field got corrupted. It affected over half of my 1000 records that had data in this field.

I used the dMC to create records in another table so I have a backup of what was selected. Going back through my data I realized that the dMC and the table were no longer in sync. 

It looks like the dMC had all of their selections increased by 1 record. Weird. Which can have the effect of having the dMC report a selection of a record that is not in view. If you have a dMC filtered, but do numbers(dMC) it will show a record Id that is not in the visable dMC.

Anyways, Ninox has said:

Most likely the state of the fields was caused by the deletion of choice values although these values where still chosen in the fields.

We have already been able to observe exactly this cause in other cases.

No explanation of why it happened. I did not modify the root table of the dMC.

Lucky for me the selections is not where I keep my data. But for those who do you just be aware that this is an issue.

6 replies

null
    • Ninox partner
    • RoSoft_Steven.1
    • 1 yr ago
    • Reported - view

    Thanks for the warning Fred 馃憤

    • Consultant and developer
    • Javier
    • 1 yr ago
    • Reported - view

    Thanks for the warning... just about to release an app for a customer that relies in lots of dynamic multi choice fields...

    • Mel_Charles
    • 1 yr ago
    • Reported - view

    Yikes !!

    was just about to link a dynamic drop multi choice to one of my tables that has over 500k records in it and then update it. think I will hold off a while

    • Fred
    • 1 yr ago
    • Reported - view

    An update, looking over my root table I did make changes. And I do make changes all the time. Sorry for the incorrect statements earlier.

    So it looks like if you never delete records from the root table then you will be fine.

    Don't know how long this has been an issue.  But we will never know when it gets fixed since they never give detailed release notes between major versions.

    • Fred
    • 1 yr ago
    • Reported - view

    Well I asked if this was fixed in 3.8 and was told to test it out. Huh? Anyways.

    Since I can't get a straight answer, I did a test and so far it looks like it is fixed. Granted it is a small test but so far when I add new records and delete records to the root dMC table the previous selections seem to stay put.

    So since the app is still in 3.7.x, this does not apply to you.

    An interesting not is that if you delete a selection it does not show it, that is good. But if you do numbers(dMC). It will show that you selected the previous deleted record. I guess that is good, but be aware of that.

      • Mel_Charles
      • 1 yr ago
      • Reported - view

      Fred Still holding off for a while - once bitten and all that !

Login to reply

Content aside

  • 3 Likes
  • 1 yr agoLast active
  • 6Replies
  • 175Views
  • 5 Following