No it’s a bug, as a workaround you can use optional columns in mappings. Required columns make Grist hide the widget temporary (to show a warning about not mapped columns) and it is loosing it’s state. I’ll either fix this (if it is possible) or dynamically rewrite the configuration from the embedded widget to change required columns to optional.
1 Like
Maybe because of the temporary columns, but I have tested and tested and I am unable to send data to a column… even thought the widget has full access. I can read data with no problem however.
I guess ideally the widget already serves the purpose of making tests… I guess after the tests, I should create files with code for real custom widget accessed from a URL
I created a simple example how to update data:
https://public.getgrist.com/d1t1x4BvxuMK/JsFiddle
Let me know if that helps, I’m curious what doesn’t work in your setup.
1 Like
Thanks Jared. I gave your example to ChatGPT and it was able to fix it.
1 Like