I’m happy to say I’ve finally had some time to give the RUC some much needed updates and polish. So we can welcome version 2.0! Loaded with new and usefull features, such as:
Working with the current table and column (i.e., the column that the formula is running in) without having to state their names.
Getting detailed information on references, such as the foreign table and column pointed to by a source, or a list of foreign records pointing to a source.
Sanitizing input data for use in reference/reference list or choice/choice list fields, optionally with the ability to auto-create any missing referenced records or choice items.
Compiling “mini formulae” from user-submitted text fields.
And more!
It’s “beta” for now because I haven’t tested it all that thoroughly. If you notice any quirks, please report them. Thanks!
From here on out, the RUC will be available in a clearly versioned fashion via this public Grist document.
I’ll leave the old repo up so people can still find it, but it’s deprecated from now on.
I’m finally taking the time to dig into your RUC idea which is a very interesting one indeed! Some quick comments on the v2.0:
It’s hard to understand how it works only with your public Grist document. I read the README of your old repo and that should probably be kept somewhere.
Following the link of your public Grist document leads you to an uncategorized page (how does it exist?) with 2 views “RUC Components” and “Formula” but the navigation bar only shows the “Showcase” pages and subpages. So once you leave that 1st page (which is really the useful one) you cannot find it back.
Rather than copying/pasting all the formulas into our own table, can’t we have the final table ready to be downloaded?
Thanks in advance for your feedback and for your work!
glad you like it! You’re making some very good points there, will take a look ASAP. I’ll admit that the invisible Grist page is rather a mystery to me, too!
EDIT: Well, that was a quick fix at least for one of these issues. It turns out that if you subordinate a page to another that isn’t publicly visible, then the entire page vanishes. Who knew?
EDIT 2: Concerning your third point, unfortunately I don’t think I can offer you that. While I agree it would be much nicer to have a downloadable document, my current workflow has me developing the RUC in a non-public Grist document and then “pushing” it to the public page I posted using some formula magic. This formula would have to make an exact copy of the RUC table as I see it and additionally have ACL applied in a way that makes the copy publicly available. I don’t think this is really feasible. Sorry!
EDIT 3: But your no. 1 point is definitely happening. I’ll move the old description texts over.
Thanks a lot for this quick move! That’s indeed better now
Regarding the downloadable table, I found out it’s harder than I thought because when I download the view as .csv or .xlsx it doesn’t download the code but only the displayed content of the cell which is <class 'usercode.RUC.Code.<locals>.Code'> for example.
So to get a ready-to-go table I think the easiest way is to have a dedicated document with that table only that could can fully download as a document.
I’ll move the old description texts over.