Skip to content

Help shape the future of Box

Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!

See user guide here.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

163 results found

  1. 68 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Search  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    beta  ·  Adminramato (Admin, Box) responded

    This feature is available for a limited set of customers. Contact your Box representative for more information.

  2. Search - Add Microsoft Visio Files (.vsd, .vsdx, etc.) to the 'Full Text Search' Index

    Box already has in-file search ('full text search') on other Office file types (Word Docs, PowerPoint files, and Excel spreadsheets), so users expect that Visio files (which are part of the Office suite) would also be indexed by Box.

    REQUEST: Include contents of Visio files (.vsd, .vsdx, etc.) in Box's search index.

    Context - here's the externally-documented list of file types supported by Box's in-file ('full text search') feature: https://community.box.com/t5/Managing-Your-Content/Search-Overview-and-FAQs/ta-p/354#search_hdsiw

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Search  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    not planned  ·  dgautham responded

    Thanks for the feedback! We have and added this to our backlog. Due to low customer demand for these types, they are currently not prioritized on the roadmap.

  3. Metadata key values of type {number, date} only searchable by range (gt, lt) and not equality

    Assume I have a metadata template "Template" with a key - value of type Number. In both the web app and API, it is not possible to do an equality search:

    templateKey = template
    filters = {"value": 2}

    Instead, the search requires specifying both lower and upper bounds. If you're searching for a single value, you then have to approximate it with a gt = 2, lt = 2 combo.

    a) Most importantly, the API documentation implies that the range parameters are not required when searching by number or date.

    b) I think both the webapp UI and the API…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    gathering feedback  ·  1 comment  ·  Search  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 5 6 7 9 Next →
  • Don't see your idea?