Honesty I thought the # commented out the yaml, but I could be wrong about that. I was just keeping it there for the time being until I decided for sure that I wanted to use the title instead. Btw, that plugin is called Front Matter Title. I got rid of the #aliases though since I am feeling more set on title now
I just went through and turned off each plugin one by one to test, but that didn’t fix it.
And yeah good point for the values being an array. I was just doing that out of habit since thats what I always used for my aliases since if I had one I would usually have another. That is also all fixed now so thanks for pointing that out. Sadly none that fixed the problem with dataview.
There’s something wrong with data.
Isn’t a query fault.
Try in a new vault without any other plugin (only dataview) and only with the aliases and eval fields in frontmatter.
(write new values without copy-paste)
Ohhh yup! I didn’t try in a new vault or anything, but I uninstalled dataview and reinstalled it and now it mostly works. Only thing that isn’t quite right now is that little work around to get an alias as the file link in the table. I switched it from:
TABLE WITHOUT ID link(file.alias[0], file.name) AS "Responses", eval
FROM outgoing([[]])
SORT eval desc
to
TABLE WITHOUT ID link(file.title, file.name) AS "Responses", eval
FROM outgoing([[]])
SORT eval desc
since I am no longer using an alias or have any of the metadata set as an array, but its just putting “-” rather than the expected link
This did the trick! Thanks for all your help!!!
TABLE WITHOUT ID link(file.name, title) AS "Responses", eval
FROM outgoing([[]])
SORT eval desc