Storing inputs in db

You got very, very close, though!

This is actually a common occurrence. The solution is to code up a data conversion function, from the type that Anvil doesn’t support, to one that it does. And probably a reverse conversion, to use the data at the other end.

In general, “It didn’t work” is usually the result of one of the following:

  1. It’s impossible, even in principle
  2. There’s a bug in my code (I didn’t code it the way it needed to be coded to make it work)
  3. It’s possible, but there are other, more practical solutions.

In my experience, #3 and #2 are very common situations.

There can be very good reasons for #2, of course: lack of information, lack of time, lack of an accurate or complete mental model to inform the design or implementation, lack of other resources, silly goofs, interruption from higher priorities elsewhere, … I’ve been prey to all of them, from time to time. This doesn’t mean the task was impossible, or hopeless, just that I didn’t complete it. On that particular attempt.

Yup, could probably convert to json before transfer to anvil and filter out the settings. These are things to explore, it’s also fun doing so. But in this case I need to continue and get the job done. The solution above works great, so the function is there. I could also do it with a list. Anvil is such a great tool for what I’m doing now, and I have so much to learn.