<![CDATA[Admin VS front-end input inconsistencies...]]>In the admin, the database editor saves "Dropdown multi" type as ["value","value2"]

But in the front-end, the Cloud backend form input "Multidropdown" saves the values as value,value2.

The admin type:
Image 2020-10-12 at 3.29.41 PM.png

Input form on front-page:
Image 2020-10-12 at 3.31.15 PM.png

In the database it looks like:

Image 2020-10-12 at 3.32.32 PM.png

First one created with input form, second created inside the admin editor.

How to make it consistent?...

]]>https://community.appdrag.com/topic/398/admin-vs-front-end-input-inconsistenciesRSS for NodeTue, 15 Sep 2026 00:04:11 GMTMon, 12 Oct 2020 13:28:42 GMT60<![CDATA[Reply to Admin VS front-end input inconsistencies... on Sat, 14 Nov 2020 14:11:37 GMT]]>@Wassim Wonderful, thanks!

]]>https://community.appdrag.com/post/1858https://community.appdrag.com/post/1858Sat, 14 Nov 2020 14:11:37 GMT<![CDATA[Reply to Admin VS front-end input inconsistencies... on Fri, 13 Nov 2020 11:48:29 GMT]]>Wow bravo @Wassim !

]]>https://community.appdrag.com/post/1853https://community.appdrag.com/post/1853Fri, 13 Nov 2020 11:48:29 GMT<![CDATA[Reply to Admin VS front-end input inconsistencies... on Thu, 12 Nov 2020 20:36:41 GMT]]>Hey Thomas,

Great news, this is now available :

ba076907-2c01-4fd0-8151-3beee702db57-image.png

]]>https://community.appdrag.com/post/1844https://community.appdrag.com/post/1844Thu, 12 Nov 2020 20:36:41 GMT<![CDATA[Reply to Admin VS front-end input inconsistencies... on Fri, 16 Oct 2020 09:33:58 GMT]]>@Wassim said in Admin VS front-end input inconsistencies...:

JSON.stringify($("select[name='searchableList']").val())

Thanks a lot for the workaround, works as expected!
Plus gave me some new ideas, neat the we can do formulas there, didn't even notice!

I love that there are these hidden gems in Appdrag 🦆

]]>https://community.appdrag.com/post/1547https://community.appdrag.com/post/1547Fri, 16 Oct 2020 09:33:58 GMT<![CDATA[Reply to Admin VS front-end input inconsistencies... on Thu, 15 Oct 2020 11:42:37 GMT]]>I can't promise to do it before end of next week because many other points are before in our task list.

If you already need it to save it this way it's pretty easy:

1 - Switch your source type from field to formula

d900345e-240e-4d90-8124-fce99aa6282e-image.png

2 - Replace searchableList by your input name and use this code in the formula

JSON.stringify($("select[name='searchableList']").val())

3 - Your data will be sent the way you expected

ad2362c8-134c-494f-9889-9e32891024bf-image.png

]]>https://community.appdrag.com/post/1541https://community.appdrag.com/post/1541Thu, 15 Oct 2020 11:42:37 GMT<![CDATA[Reply to Admin VS front-end input inconsistencies... on Thu, 15 Oct 2020 08:42:18 GMT]]>@Wassim Such an option would be perfect! Covers all bases.

How quickly can you add it? We need to launch yesterday...

]]>https://community.appdrag.com/post/1535https://community.appdrag.com/post/1535Thu, 15 Oct 2020 08:42:18 GMT<![CDATA[Reply to Admin VS front-end input inconsistencies... on Tue, 13 Oct 2020 08:17:10 GMT]]>Hum, I wouldn't say the form input you're using is initially specifically targeting this type of column but I agree that it would be great to have it consistent.

What do you think if we add an option on the field to determine if it saves it "value, value2, value3, ..." or ["value", "value2", ...]?

]]>https://community.appdrag.com/post/1511https://community.appdrag.com/post/1511Tue, 13 Oct 2020 08:17:10 GMT