REMINDER

Please be respectful of all AppDragers! Keep it really civil so that we can make the AppDrag community of builders as embracing, positive and inspiring as possible.

CloudBackend and CloudDB use different quoting settings for multi-select fields



  • Perhaps related to the other dropdown issue

    It seems Cloud Backend's UI and CloudUI treat the multi-select fields differently.

    CloudBackend escapes the integer Primary Keys, but the CloudDB UI does not. I ended up with something like this if you use both on a single row:
    Screen Shot 2021-04-29 at 12.59.57 PM.png

    Also, because the dataType in SQL is medium text, not JSON, it's very difficult to parse.

    Can you please make it consistent (integers alone, without quotes, is preferred but any consistency is better than this) and also can you tell us if it's possible to add a JSON data field type? Aurora SQL supports MySQL 5.7+ now including JSON field types 🙂



  • Hello,
    We now use consistently strings in our array so you would have everywhere ["298", "5"] if you use CloudDBUI or not.
    About the JSON type, I added it to the list and we'll check what impacts it would have.



  • Thanks Wassim ! I will check it out and hopefully I can make everything work now for my scripts 🙂



  • Hi @Wassim, while we were waiting for the fix, I switched one of the fields back to linked 'field' (singular), but unfortunately, now that column is blank in CloudDB (but not in CB).

    The data in each field is just an integer, no brackets, etc., and it shows up correctly in CloudBackend.

    Screen Shot 2021-05-10 at 1.27.06 PM.png



  • Hi,
    Ok I added a fix to handle them even if they're string instead of integers. It will be pushed in production tonight.


Log in to reply