Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6162 Ideas

    mewingContributor ⭐️

    Ability to Reorder or Alphabetically Sort Custom Views in Renewal Center → ForecastNew Idea

    Our team heavily leverages the Renewal Center → Forecast module to manage renewal pipelines and review opportunities. We’ve created a standardized set of saved views to guide our renewal process — for example: 01 – All Opportunities 02 – Renewals 03 – Multi-Year Proposals 04 – Off-Cycle (Suspension & Backdated) 05 – Churn etc etc However, the Views dropdown (“My Opportunities Views”) does not currently allow any control over the order in which these views appear. The list seems to be displayed based on creation order or a partial alphabetical sort, but not consistently.We have already prefixed view names with numbers (“01 – …”, “02 – …”, etc.) to enforce a logical sequence, but the UI doesn’t respect that order. As a result, Renewal Specialists see an inconsistent list, which creates confusion and inefficiency during forecast reviews.Proposed EnhancementPlease add one or more of the following capabilities to the Renewal Center → Forecast page: Manual reordering of views (e.g., drag-and-drop in the dropdown list). Option to enforce alphabetical sorting of the “My Opportunities Views” list. Ability for admins to set a default order or pinned favorites visible to all users. Business Impact Enables consistent workflows and standardization across Renewal Specialists. Reduces confusion and time spent finding the correct view. Improves adoption of Renewal Center and ensures accurate forecast reviews. Supports scalable operations for large renewal teams following predefined sequences.

    Tomas Trijonis
    Tomas TrijonisContributor ⭐️⭐️⭐️⭐️⭐️

    Fix report row loading and paginationNew Idea

    As you know, running a report will only actually load a limited number of rows despite the real count of records. In theory, when you scroll to the bottom it should load the next bunch of records, and so on as you keep scrolling.In my experience, this actually rarely happens. A common scenario is finding myself scrolled to the bottom of a report with thousands of records (shown in the count in the top-right), but seeing maybe a  few dozen of lines. And any further loading just never happens. I’m stuck.What I found fixes this sometimes is:Zooming out/in in the browser to trick the HTML into loading more records Setting an actual record “Limit” setting.It’s kind of ridiculous, but this bug has been here since the change to get rid of pages in reporting. To hijack my own post in order to complain (ehem, provide feedback) - pagination had a clear benefit for me as in I could always tell how many records am I looking at at any given moment.If I had 599 records total, I would know that on 200 records per page I would need to traverse precisely 3 pages to check all the data. Now the answer is “who knows how many goddamn scrolls”.If I had 599 records total, I would know that the client “Blorp Corp” will be on the first page sorting alphabetically, whereas the client “Zlorp Corp” will be on the last page. Now it’s just “scroll until you find it” or use search which is not efficient in some cases.Now every scroll is a painful 50 records loaded, stat. No more changing to “200” per click. Womp womp. I don’t know, maybe I just don’t see the real benefit of this, or maybe “doomscrolling” a report is the new craze?

    Marion S.
    Marion S.Contributor ⭐️⭐️⭐️

    Global Option to Filter Users Across PX AnalyticsNew Idea

    We’d love to have a global way to filter out internal users across all PX analytics and reports.Right now, there is no way to automatically exclude internal users from PX data globally. The only workaround is to manually apply filters in each page (for example: “Email does not contain ‘@ourcompany.com’” or “Account name does not contain ‘Internal’”). However, this option is not even available for all pages, for example, not in the account explorer.This is time-consuming and error-prone, especially when multiple team members need consistent reporting.Why this mattersIn our case, many of our internal users—especially CSMs—regularly interact with customer environments. Their actions generate a lot of activity that skews the analytics we want to share with product and customer success teams.Being able to automatically exclude internal traffic and actions would help ensure our data reflects real customer usage and insights.Suggested solution A global “Exclude internal users” toggle or rule applied across PX Analytics. Ability to define internal users by criteria (e.g., email domain, account name, or user tag). Many other analytics tools offer this type of functionality, and it’s extremely useful for keeping reports clean and trustworthy.Thanks for considering this enhancement — I believe it would add great value for all PX users!