Specify 6 EOL questions - Attachment Mapping files and Repeat Label Printing

Hello!
Hope all is well - keen for the Open Office Hours this week.
This is less of an actual question but I figured it would be good to just mention a few things that are our main reasons for using Specify 6 ahead of time and to see if there are any updates that I might’ve missed.

The two main issues that keep popping up for regular use of Specify are

  1. Label printing still doesn’t accept countAmt, so we’ve had to use workarounds to try to print multiple labels - batch printing has worked for us, but it means that we have to print all labels even if we only need one. I’ve been following the issue for this (Cannot print based on `countAmt` value · Issue #3434 · specify/specify7 · GitHub ) - are there any updates or things that we could be doing to get this to work? and

  2. Not having an Attachment Mapping file capacity still stops us from doing bulk image uploads from Specify7, as the required format needs either to add the leading 0s or removing the ‘BRI-AQ’ from the start of the image file, which would break too much of our existing process.
    I’ve been keeping an eye on Add Attachment Mapping File support · specify/specify7 · Discussion #5941 · GitHub and previously Add Attachment Mapping File support · Issue #4766 · specify/specify7 · GitHub. I don’t really have a question in particular to ask here other than if there’s been any updates or progress on this, or if there’s any way to do a workaround using different fields if the attachment mapping file isn’t likely to come soon? If there’s another ticket or discussion to follow let me know as well - I’m not sure if i’m following the correct issue/tickets for this one.

Those are the two main things that I’m curious about - we are also having an issue where large loan returns will crash Specify7 as they overload chrome while trying to populate the loan preparation (in the loan example given to me there are 1934 loan preparations) statuses which I believe is probably an issue with the sheer size of the loan- although if you have any ideas on optimisation or things that could stop it from happening I’d appreciate it!

Appreciate all the help with these - apologies that I don’t really have any concrete questions to ask beyond checking for updates.
Cheers,
Leo

Hi Leo,

  1. This has been added to the timeline for 7.16.1!
  2. Attachment mapping file support is in our long-term plan, but as of now there is no workaround.

As for large loans crashing, this is a known issue that’s been written up on Github . The one workaround to this would be to change the loan preparations from a table to subview. As a subview, only one preparation would show at a time, so it would not attempt to load all 1,934 preparations at once which is causing the crash.