Creating object from forwarded email has stopped working
complete
M
Mari Nakamura
2024 M3 iMac, Sequoia 15.6.1
Creating an object by entering [[object/Name of object]] or +object/Name of object/ in the body of an email forwarded to Capacities has stopped working. The email appears on my Daily Note, and when I remove the email, I see the new object listed in the nested content, but it has no assigned object type. If I search for the new object, I can find it, but it appears blank and has no assigned object type.
Log In
Luis Martín
marked this post as
complete
Luis Martín
Hi Mari Nakamura,
Thank you for reporting! Unfortunately we weren't able to replicate this behavior. Could you answer the following? please update to the latest version of Capacities before you do:
- Does the email contain any text or reference to the object?
- After the update, are you able to visualize the objects that were imported?
- Does the created object appear in the Object Type's dashboard?
- If you search for the new object and try to change its type to the right type, do you get any errors?
Thank you once again and sorry for the inconvenience!
M
Mari Nakamura
Hi Luis Martín - Thanks for investigating!
- Yes--as shown in the screenshot titled "Bug - Object not created from email" that I attached when first submitting this ticket, I included [[Object/Name of new object]] in the email. This is the format I normally use, but in trying to troubleshoot this bug, I had also tried the other two options, +object/Name of new object/ and @object/Name of new object/, and these didn't work either. I've attached one of my test emails to this comment.
- As shown in the screenshot I'd originally attached, I was able to visualize the new objects in that they were listed as a nested object if I started removing the forwarded email. However, they weren't assigned an object type, as shown in my screenshot, and if I searched for them by "Name of new object," I could find them, but they appeared blank (contained none of the properties for the object type), and I didn't have the option to assign/convert to an object type.
- Since the created object was not assigned an object type, it did not appear in any object type's dashboard.
- See answer to #2.
Since submitting this ticket, I've continued to install new Capacities updates as they've become available. Sometime after the most recent one (version 1.56.1), although not immediately after, I noticed that a new basic object type called Task now appears in my database, and that some of my missing new objects now appear on that object type's dashboard (see attached screenshots).
As it happens, the objects that I had been trying to create were of a custom object type also called Task. This makes me wonder--am I inadvertently bumping into a new Task basic object type that is under development? In other words, were my custom Tasks not being created because Capacities was trying to instead create objects of the new basic Task object type that didn't quite exist yet back in November but now does sort of exist? From what I can tell, I don't think the new basic Task object type has actually been rolled out yet: I see that Task Management is still listed as Planned on the Capacities Roadmap, AND when I click "+New content," only my custom Task object type and not the new basic Object type are in the list of object types that can be created.
Luis Martín
Hi Mari Nakamura,
We deployed a potential fix for this, could you check if it's all working now? Thank you!
M
Mari Nakamura
Hi Luis Martín,
Yes! The fix seems to be working: When I forwarded an email to Capacities today that included [[task/Test task.]], a task (of my custom Task object type) was created.
I see that in the meantime, the new Capacities basic Task object type and task management features have been deployed. Is the fix that if a user has a custom Task object type, including [[task/XXXX.]] in an email creates a new task of the custom type rather than the (now) built-in basic type?
Thanks,
Mari
Luis Martín
Hi Mari Nakamura,
Glad to hear it's working well now :) thanks for confirming!
We now match objects based on title for matching object types names, so unless you're creating a new task in the email it should derive to the right object type. Otherwise we'd recommend that you switch the custom object type's name to be 100% certain that the new objects end up in the right object type, but there's be a preference to custom types.
Beth
marked this post as
under review
Beth
Mari Nakamura can you reproduce this issue today or was it a one-off situation?
M
Mari Nakamura
Beth - Thanks for following up so quickly on this ticket. I just checked, and sadly, this issue persists today.