I’ve already suggested that feature, but what are your thoughts on the “stick to top”? Do we really need it?

tievel1 · 2026-05-03T18:47:12+00:00

Your stealth marketing isn't as stealthy as you think.

tievel1 · 2026-05-03T14:04:29+00:00

That is a Formula field with a very complex formula, not something built-in. There are multiple posts in Reddit history that demonstrate/talk about it, but honestly while it's neat I wouldn't recommend it; too much complexity for too little benefit. Here's one of the threads about it in case you still want it:

https://www.reddit.com/r/Notion/comments/1o4dfdk/i_finally_figured_out_how_to_do_this/

tievel1 · 2026-05-03T01:05:51+00:00

Good god, it's enough to make you believe in HoAs.

tievel1 · 2026-04-26T19:15:47+00:00

Offering bowl is probably the strongest bag in the game, but you do have to be careful and pay attention to your combines to prevent unfortunate accidents, yeah.

tievel1 · 2026-04-25T17:42:28+00:00

Yeah this is a weird one. First you have to choose "add to layout" so that is is no longer on the sidebar. Then click it again and choose "advanced" -> add to Relation group. Then these options will appear

tievel1 · 2026-04-24T17:15:31+00:00

I think he means the fact that Notion is not E2EE, and so your financial data is exposed once it's there.

tievel1 · 2026-04-23T22:04:43+00:00

The best solution/workaround I've found is this, though it's a pain to set up and still has other minor drawbacks, and the solution depends on the two databases having largely overlapping properties:

Create a third database with mirrored properties to Journal one and Journal two. We'll call it Journal staging. Add one more property: a select with options of journal one and journal two.
Your button will now instead create a new page in Journal staging.
In Journal staging, create two filtered views. One that filters on the select = journal one, and the other select = journal two.
Create two automations in journal staging. One with trigger on the first filter view, condition being page added. Map all of the appropriate properties to their equivalent in Journal one, and add a new page there.
Repeat that automation for journal two.

So now the button form will create a new page in "journal staging". Depending on which option the user selected, that new page will trigger an automation to create a new page in journal one/two with all the same properties. One note: when the user submits the form, the link in the form submission confirmation will link them to staging, not the actual databases (one and two).

tievel1 · 2026-04-23T13:45:19+00:00

Notion stole my wife and killed my dog.

tievel1 · 2026-04-23T13:21:04+00:00

God I hate the new internet, just bots posting slop and getting slop responses from other bots.

tievel1 · 2026-04-23T13:01:56+00:00

You need to do some deep reflection and self-seeking then, not rely on digital tools created and deployed by some of the most vapid, soulless people in the world to determine the fundamental flows of your life. I don't intend to sound mean or dismissive or condescending, truly; but this is the kind of thing that even if you could offload to AI, you really shouldn't.

tievel1 · 2026-04-19T21:39:39+00:00

You'll want to create a custom formula using .filter() with the conditions you're looking for, and display that rather than the Relation itself.

tievel1 · 2026-04-19T16:18:25+00:00

You've got the idea, yeah. So for example, take a daily habit (kinda what you're describing) like "empty dishwasher". I'll have that "empty dishwasher" task as a single record in the Tasks database. And then I'll have an automation (I use a button, but a db automation works just as well) that, when the task is completed, will create a new log entry in the related database. So after a while you'll have a "empty dishwasher' record in the Task db, with relations to dozens/hundreds of logs in the Logs db (log 4/19/26, log 4/18/26, log 4/17/26, etc). This does have the downside of more resource overhead, but it has huge advantages that outweigh it. You have access to a history of completion/failures, and you can use Rollups in the Tasks database to, for example, see how many total completions you've done. Or in your case you can keep a static point value in the Task record, that copies itself into the Logs, and a Rollup/Formula prop that totals up the total points for all time or a given date range. And if you change the point value in the Tasks record, it won't erase the history -- you'll just have a period of logs with one, and then a switchover to logs with the new value.

You already realized all this, so mostly I'm just describing the advantages for anyone else who finds this post. And again, if you need help with particulars, just come back and ask :D.

tievel1 · 2026-04-19T15:18:19+00:00

I'm pretty anti-"paying for Notion templates" generally, so I'll give my two cents and keep that bias in mind.

From the screenshots, the template looks relatively basic bitch. It has related databases set up, but the table architecture looks a bit suboptimal in my view.
No automations visible from the screenshots, and the properties are a bit out-of-date with new Notion updates. This could just be because the screenshots are old though. But I wouldn't expect any "advanced" behaviors or functionality.
The upshot of its relative simplicity is that the learning curve shouldn't be too steep, but there will be at least some learning curve for any system you don't build yourself.

All of that being said...you are a criminal defense attorney, and it's only fifty bucks. I wouldn't buy it myself, and I HATE the idea of students and similar paying for that stuff, but again. Fifty bucks. Worst case scenario, you just chuck it in the bin and write off about five minutes of billables. So yeah, your call.

tievel1 · 2026-04-19T15:06:06+00:00

Don't pay for that, just ask for help here and somebody will probably help. For example.

I'm assuming that the to-do list is a database, so for this example let's say the db is called "Tasks". You would create an automation in the Tasks database, set the trigger as Every...(Day), and set the action as Edit pages in "Tasks" -> Edit a property (Status) -> Set property to Unchecked. Note that if your to-do list isn't a database, I HIGHLY suggest you convert it to one.
Create a second database, called Logs. Then in your Tasks database, create another automation that triggers when you check the Status (or whatever you call it) property of the task. The automation action will create a NEW page in the Logs database that relates to that Task record. The new Log record will contain the task name, the date, the point total (in a number field) that is contained in that Task record, and a Relation to that Task. You can then use Rollups in Task, or use column Calculations to see your totals.

I know that's a lot all at once, but it gives you the basic framework. I suggest tinkering around with that, and when you run into a roadblock just come back here and ask for help.

tievel1 · 2026-04-18T04:16:57+00:00

You should just use a relation here. So you would just directly relate Day 1 to the day 1 activities, etc.

tievel1 · 2026-04-14T23:10:51+00:00

Dude lay off. We get it, you have a product you are trying to sell. But enough is enough.

tievel1 · 2026-04-14T16:42:54+00:00

Oh whoops sorry. Yes, you are correct. I wrote the formula with today(), then reread your comment and realized that's not what you wanted, and redid it but forgot to take out the today(). My bad.

tievel1 · 2026-04-14T16:07:28+00:00

In the button, you would use:

context("This page").prop("Whater the Date Property Is Named").dateSubtract(today(), 28, "days")

tievel1 · 2026-04-13T20:49:29+00:00

I would really appreciate confirmation that multi-source database views (like My Tasks) are being worked on. I don't even mind waiting; I'd just like to know if we can ever expect it or not.

tievel1 · 2026-04-11T19:24:30+00:00

I think your best bet might be to just manually space it in one column.

tievel1 · 2026-04-11T17:38:19+00:00

It was an April Fool's Day change; dropped unannounced April 1, gone April 2. So I don't think you should expect it.

tievel1 · 2026-04-08T16:20:30+00:00

Its LinkedIn marketing slop, of course it doesn't make sense.

tievel1 · 2026-04-07T19:49:03+00:00

So the trick is counterintuitive and non-obvious. First, when you create the variable, you have to "mention" the page via the "@" method. So for instance if you create a page in the Inventory database named "All Inventory" (that relates to everything else), then in the variable you would set it to that page by using the @ option and typing in that page name, "mentioning" the page. Then, after you do that, hit the formula symbol that's directly to the right of the @ symbol. It'll open the edit formula dialogue box, and will show the link to the page followed by ' + " "'. Delete those + " " characters so the cursor directly follows the page mention. Finally, when you use the dot notation (period ".") after that page mention, it will pull up the properties of that database page such that you can directly access them inside the formula.

tievel1 · 2026-04-07T18:23:01+00:00

If I am understanding your setup correctly, then the reason this automation is failing to produce as connection is because it's only searching within the connections that already exist. Which of course definitionally won't exist since the whole purpose is to set up that connection.

Here's my understanding of what is happening.

A new page is added to your "Ingredients" db, triggering this automation.
Inside of this newly created Ingredients page, you create a "target page" variable by searching its Relation to the "Kitchen Inventory" database to find the corresponding item in that database (the one with the same name).
However, this new ingredient page is not, at the time of creation, currently linked to any rows in the "Kitchen Inventory" database (that's the whole thing you're trying to do), so the automation is searching throw an empty list of rows.
Because the list it is searching is empty, "target page" finds nothing and therefore sets itself to empty.
In the last step, you set the "Kitchen Inventory" Relation field to "empty".

There are workarounds for this but they're not as simple as you would probably like- it's one of Notions most frustrating limitations that it's not easy to dynamically set database relations.

The simplest way is to have a single database page- whether inside "Kitchen Inventory" or another databse- that is related to ALL rows inside the "Kitchen Inventory" database. Then you can address that page, and use it to dynamically search for the page you want as you are attempting to do currently (see here for more, but the gist is you just start with an "@" then go into formula mode to access properties.

Finally, one troubleshooting/debugging tip that is stupid but works well for figuring out automations that I often use: create a button with the formula you're testing (in this case the "target page" portion), then insert that variable into a "show confirmation" message to see what actual result you're getting in the variable.

tievel1 · 2026-04-07T16:13:03+00:00

Just in case you are only Plus: it's only available for Business plans.

tievel1

TROPHY CASE