🪲 Bugs
Under Review

v1.63.3 - Feedback on improved import tool - import from Anytype

Overall, the import of a page object from Anytype has improved.

  1. Images from an Anytype page are created as image objects in Capacities and show up as links in the object in Capacities, which then can be manually converted into image blocks.
  2. Weblinks from an Anytype page are created as page objects in Capacities, but not as weblink objects and show up as inline links on the object in Capacities, which can be manually converted into embedded Weblinks.
  3. In Capacities, I have a custom object type named "Artikel". Since I want to use only this type, I selected "Force Object Type" in the import form.

However, by doing so, the results differ depending on the UI language setting of Capacities:

  • Force Object Type "Artikel" with interface language English -> results in originally embedded images being displayed only as text path on "Artikel", but not imported as objects. Therefore they don't show up as images on the Capacities object. But if I let "Force Object Type" unchecked, Capacities creates two different objects, "Artikel" and "Page", which I don't want to have. This does not occur with the German language interface.
  • Force Object Type "Artikel" with interface language German -> results in originally embedded Images being correctly created as objects, which then can be manually converted into blocks in the object "Artikel".

1 Comment

Sign in to comment

PM
Paul McDonald·4 months ago

I’ve voted for this, as it would mean that I could then move over all my page objects into Capacities (those are the only objects I can’t use in there atm)

When I imported my pages from Notion into Anytype, it was pretty much flawless - nothing had to be changed really. I tried with a few from Anytype into Capacities and it just wasn’t the same experience at all, I just had to give up in the end