I have no idea. But I can describe the situation.
I have had a vault using Dataview for at least a year.
I defined a field as MultiFile and until last time, that is about 3 months ago, I could click and select multiple items as internal links. Today however doing so gives error “Type not expected, expected Text”.
I tried opening a new tab with an old file where it had multiple items and even there it gives that error, which it had never given.
I tried clicking on the field and it changed.
If that was not enough, doing Ctrl+Z went back to another tab and not the one with the focus!
Since this is an error that occurred on an old project, I can’t test it in the sandbox
Expected result
I want to be able to put multiple links in a Multifile field.
I expect the old files to continue to work
Actual result
Error “Type not expected, expected Text”.
Environment
SYSTEM INFO:
Obsidian version: v1.8.10
Installer version: v1.8.3
Operating system: Windows 10 Education 10.0.19045
Login status: not logged in
Language: it
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 1
Restricted mode: off
Plugins installed: 11
Plugins enabled: 7
1: Dataview v0.5.67
2: Templater v2.10.0
3: Auto Class v2.3.0
4: File indicators v1.1.0
5: Folder Note v0.7.3
6: File Explorer Note Count v1.2.3
7: Metadata Menu v0.8.7
A quick summary for people who are trying to help you:
You have a list-type property whose values are links. But the property is showing the “Type mismatch” error / “Tipo non corretto”. And when you click on the property values, their format changes.
It makes me wonder if your YAML format wasn’t right for Obsidian.
For example, this format works in Obsidian:
---
esempio:
- "[[a]]"
- "[[b]]"
- "[[c]]"
---
But this format gives a “Tipo non corretto” error.:
Does the first format above work in your vault?
Does your list property use that same format?
I don’t recall what the error was like in v1.8.10, and I don’t know what might have changed the format for you (maybe a plugin?, maybe an Obsidian update?), but checking the format might at least explain why you’re seeing the error.
I also verified on an old file, up to 3 months ago it worked, today opening it gave error, yet the format is the one that 3 months ago obsidian accepted and that you also confirmed to me to be correct.
I checked the updates. Obsidian seems to be installed. I’ve also done the plugin updates for that vault, I hadn’t thought of that, and even after reopening it still gives error
When you open the “All properties” list and right click on the property, is it a Text type? Because that would cause the “Type mismatch, expected Text” error:
I don’t know what changed it. My first guesses from your plugins list are something in Auto Class, a script in Templater, or a field-type change via Metadata Menu. Or maybe something else.
