The setup sometimes work and sometimes doesn't work... Why?

Hello,

I don’t understand… when a user clic on one activity, when the activity is displayed, it should add a +1 in the next 4 column. But, like you can see on the screenshot, sometimes it do, sometimes, it don’t do… I don’t understand what happen… I do exactly the same thing and i haven’t the same result… Except the fact to display the activity, i don’t touch at al to the setup that i put to excecute this…

Someone have an idea of what happen ?

Someone have an idea?

@LuckyTravel for those who are trying to help it might be useful to provide a bit more information. You include only a screenshot of the database in your post, there is absolutely no info about the actions in your app.
My assumption will be that you have configured something incorrectly. But what and where - I can not guess.

Best,
Victor.

Ok, so, you have a screenshot of the screen when you clic on an activity (on the right of the picture), and, oon the left of the picture, you can see the actions that i configured.

So for example, when i go on the mobile app and that i select the activity “Musee d’aquitaine” (like you can see on the picture), when after, i come back on the database (the screen is in the first message), instead of to have 1 / 1 / 1 / 1, i have nothing… (just a simple 0 in the first column and nothing for the other column and the 0, it’s me that i added that manually… I also removed that but it have changed nothing…).


And like you can see in the screenshot of the database, for the activity “laser quest Bordeaux”, when i displayed the activity, it have added a 1 / 1 / 1 / 1. So it have worked correctly…

So… have you an idea of what happened ?

(if you need of more information, don’t hesitate to ask me and i will provide that to you :wink: )

@LuckyTravel from what I see actions seem to be correct (although it was difficult to understand due to property namings). I can think of 4 cases here:

  • the “Update Activity” action fails due to the uninitalized values in the database. In simple words, it tries to take value from Current Activity → X (where X is one of these properties with long name), the value is uninitialised and returns ‘null’, and Adalo can’t process this as 0, thus failing to add 1 to it. This hypothesis could be tested by creating a record with all 0s initialized explicitly.
  • the action itself is corrupt for some reason. Easy to test - just recreate the action.
  • for some reason such update doesn’t work as on-screen-enter action. This could be tested by creating a temporary action (putting it to some element), configuring it to update the record in the database and see if the issue persists or not. This is unlikely but who knows.
  • the result of a previous conditional action somehow(?) causes the non-execution of the subsequent action. I can’t imagine how this could be related. In Adalo if the action itself fails, all subsequent actions are not executed; but most common case is custom actions or collection permissions’ restrictions, which is quite rare. Easy to test: remove previous action and see what happens.

Best,
Victor.

1 Like

Hello,

Sorry for the delay of my answer. So if i understand all of what you said :

  • Try to put a 0 to complete all cases and see if it change that in 1 when i do the action.
  • Remove and recreate the same action to see if the action was corrupted or not.
  • Can you reexplain me the third case please? i’m not sure to have fully understood what you said… :confused:
  • Ok for the last case :slight_smile:

Hi @LuckyTravel,

For #3 you just add a temporary button on the screen and add the same action(s) to it like you have on-screen-enter. Kind of manually simulating the flow. If it works and on-screen-enter doesn’t (even after you recreate on-screen-enter), then the issue is related to on-screen-enter.

Best,
Victor.

1 Like

Hey @Victor,

Ok, i will try it and let you know if it works or not, thank you for your help :slight_smile:

1 Like

@Victor Almost 1 month after to have had the problem, by miracle, i did nothing, i tested the part that had a problem and all works perfectly good… Thank you very much for your help :slight_smile: