Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    DannyPancratz
    DannyPancratzVIP ⭐️⭐️⭐️⭐️⭐️

    Expanded Date Logic for Reports and Dashboard Widgets: Before/After a Specific DateNew Idea

    User StoryWhen I {make a change}Launch an engagement Map a feature / change a feature mapping (especially if the backfill won’t pull in all of the relevant data like global context from before the new definition) Change something about the UX/CX Start a community initiative to inspire product adoption etcI want to set reports and/or widgets to show data that happened {relative to that date}Before the date (Before the change) After the date (After the change)In order to easily compare and contrast user behavior relative to that date. AND so that I don’t have to constantly remember and/or update date ranges in my saved reports and widgets. Ideal RequirementsWorks with existing Daily/Weekly/Monthly view options for charts in widgets Filters those views before/after the data set in the report or widget Works with Query Builder and other Analytics as a saved before/after date of the data setCurrent State / Pain Point ExamplesA mapped featured does not have global context as part of the backfill. We want to have reports and widgets that filter based on global context. When sharing / editing dashboards, I find myself constantly adjusting the custom date range to start from that date … but the end date sticks as the day that I’m making the change and doesn’t update. So that view of the report/widget becomes outdated as soon as the next day.  Same pain point for wanting to have two reports and/or widgets that show a before and after.  Before can be set and remain static, but the after {date} would need a custom date range that’s updated regularly until the {change date} falls beyond a Last {range} setting for how we might want to view the data (last X days/weeks/month). That could be QUITE a long time if, for example, you wanted a weekly view for the next 12 weeks or a monthly view for the next 6 months (after the change)   

    christopher_sanderson
    christopher_sandersonHelper ⭐️⭐️

    CTA detail view for linked objects- respecting record type limitations on picklist (and other places)New Idea

    This is going to be a doozy, but we need to come up with a way to respect the picklist values when its reading data from a specific record.  Within SFDC, the only way you can restrict picklist values is through Record Types (Opportunity, Case, Account, etc).  When our customers set up these restrictions, it is often because they are working with a legacy system.  It could also be that they have to manage multiple types of engagements for different teams but want a unified reporting system. This idea is focused on the CTA Detail View for when we add a linked object record to that CTA (although it could apply to other parts of the product).  Today, when a customer pulls that linked record into the CTA, say an Opportunity record, and displays field level information, say Stage, it is going to show the entire picklist set of options that SFDC has.  However, if the user was on the actual record in native SFDC, they would only see the allowed picklist options. While there are some workarounds I came up with to get around this, the two big issues I have run up against are: It's not a real time update, as you would need a rule to write data from one field to another If there are multiple picklists, across multiple objects, this becomes cumbersome to manage and will generally require a SFDC admin's time, which is not always feasibleWould love to discuss further.