jxpeng98 / obsidian-to-NotionNext

Share obsidian markdown file to any Notion database and generate notion share link 同步obsdian文件到任意Notion数据库。
GNU General Public License v3.0
49 stars 5 forks source link

Error message: tags is expected to be relation. Even though the notion database has tags in relation! #38

Closed pratyushV-l closed 1 month ago

pratyushV-l commented 1 month ago

Hi! I am reporting an issue when trying out the plugin for the first time. When I try to publish a note to notion, with both the title and tags metadata correctly filled in, and the notion database having the right naming and types, I still get the error - Error message: tags is expected to be relation. Please help me in fixing this, I have attached some resources below to better understand the problem.

Notion Database- https://right-venom-936.notion.site/11b3b6338f47818eabafe4d59c782738?v=11b3b6338f47816e8a81000cb4944a17 Obsidian - image

pratyushV-l commented 1 month ago

Also for reference, I have selected the general database structure

jxpeng98 commented 1 month ago

@pratyushV-l Thanks for using the plugin.

You set the wrong property for tags.

In your Notion dataset, you set tags as the relation.

image

You should set it as the multi-select.

image
pratyushV-l commented 1 month ago

Thank You, I have bypassed the issue now. I am facing another issue with the error: plugin:share-to-notionnext:21712 Uncaught (in promise) FetchError: request to https://api.notion.com/v1/pages failed, reason: write ECONNABORTED at ClientRequest.eval (plugin:share-to-notionnext:21712:16) at ClientRequest.emit (node:events:529:35) at TLSSocket.socketErrorListener (node:_http_client:501:9) at TLSSocket.emit (node:events:517:28) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Please let me know how to resolve this, and also let me know if needed to open this as a seperate issue

pratyushV-l commented 1 month ago

Nevermind, this issue was explicitly only for that individual note, it works otherwise. Thank You!