Problem I would like to solve
Recently one of my vaults (and only one of them) has started showing the date created property at the top of the file along with all of the other properties. I do want the properties I have added myself to be visible. I do not want the date created property to be visible.
Things I have tried
I have tried simply right-clicking on that property and selecting “remove”, and it disappears directly. However, the second I leave that note and return to it again, the date created property is once again visible.
Other info that may or may not be relevant
I do not know what caused this change, and therefore I don’t know how to fix it. However, it may be worth noting that the afflicted vault is one for which I use Quartz to publish it as a blog.
The purpose of this vault is to map a database structure, and as such there is a note for each table and column in the database, and I have linked them using properties such as primary_key, foreign_key etc.
Therefore, it matters that the properties I have assigned to each note show up in the blog, which they did not do with Quartz straight out of the box. To solve that, with the help of some AI coding, I have added a FrontmatterPropertiesBox.tsx file to the quartz > components folder to make the properties visible on the blog (along with alerting other quartz files that it exists, as appropriate, though I am not 100% certain that I remember anymore which all files got modified in the process).
This worked. However, in Obsidian those properties are clickable links, and are visible in the graph view as connections between the notes. In the blog the properties are showing as plain text, with double square brackets before and after, and no visible connections between the notes in graph view.
Since reaching that stage, a couple of months ago, I occasionally try some AI assisted troubleshooting and code testing to see if I can get those links in the properties clickable. So far, nothing has worked.
However, I noticed the problem this issue is about, the sudden appearance of the date created property after the last troubleshooting/code testing session. Therefore, I suppose that something I did then may have triggered this symptom? Or, perhaps, this is just a coincidence? I don’t think that anything in the Quartz files should be able to change how/what Obsidian displays in app. But since this is the only blog for which I have done these tasks, and the only one that is afflicted with this problem, I can’t help but wonder.

