Skip to main content

CSV as Plugin Import

Comments

5 comments

  • Matt Kearse

    Firstly, I apologize for the extremely slow reply! Somehow we overlooked this question until now.

    Unfortunately you've run into a limitation in our code which detects which exporters are compatible with the type of documents the wrapper plugin accepts. We've fixed this for our next major release (2021.2) of Geneious Prime. Sorry, but I'm unable to think of a work-around for you in the meantime.

    Please let us know if you have any further questions and we'll endeavor to answer more promptly next time!

    0
  • Chow

    Hi,

    I saw the release notes for 2021.2 mentioning that this was fixed, so I excitedly updated to the beta (Geneious Prime® 2021.2.0, Build 2021-06-15 11:22).  It's still not allowing CSV as an input for wrapper plugins.  I tried creating a brand new plugin and going through all the Plugin Types, but none provided CSV as an option.  Is there a newer build?

    Thank you!

    0
  • Matt Kearse

    Thanks for letting us know. It turns out this fix passed through our QA process successfully, but we made a mistake in our release process and this fix wasn't included in 2021.2.0 like it should have been. It will be in the next patch (2021.2.1) which will probably be available in about two weeks.

    Sorry for the confusion and thanks again for pointing this out to us.

    0
  • Chow

    This is mostly working now but I've come across another issue.  Even if the plugin settings say to Export Full Table for the CSV input, fields will not be exported unless they happened to have been selected the last time a manual export was performed.

    For example, I want to export a CSV to a plugin that will use the Bit Score, Description, and Grade.  If I included those fields the last time I manually performed an export outside of the plugin, the plugin will work fine.  If I did not include those fields the last time I manually performed an export outside of the plugin, the plugin will give an error stating that those fields cannot be found, regardless of the plugin settings clearly including those fields.

    0
  • Matt Kearse

    Very sorry about that, and thanks for letting us know. Unfortunately it appears our CSV exporter has a non-standard way of handling options preferences which is causing it to not work properly conjunction with the wrapper plugins. We'll look into fixing it.

    In the mean time, the only work-around I can think of would be to write your own CSV exporter using our plugin development API. That would be quite a bit of effort to go to though. Sorry I don't have a better suggestion.

    0

Please sign in to leave a comment.