Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6166 Ideas

    Janine MarlattHelper ⭐️

    Salesforce Integration- Account and Contact- joining to other objects for push/pull to/from pxOpen

    Reading through the Salesforce Integration to Gainsight PX, I do understand that only one match record can be utilized and then only at the account as well as contact level. In the world of data wrangling, this is very limiting.  We would like to push/pull other relational fields that are not on the account or contact object level.  And require joins to other objects.For example to utilize name information like salesforce account owner name, one must do a join to the specific user table.  I am lobbying for change of the salesforce integration  to include more than a very limited inner join of a match field for account and contact objects.SELECT gsight_group.gsight_acct.acct_id as GS_Acct, gsight_group.gsight_acct.name as GS_Acct_Name, gsight_group.gsight_acct.prod_nme as GS_Product_Name, gsight_group.gsight_acct.sfdc_id as GS_SFDC_id, gsight_group.gsight_acct.duns as GS_Duns, gsight_group.gsight_acct.org_subscriber_id as GS_Org_Sub, gsight_group.gsight_acct.subscriber_id as GS_Subscriber_Id, gsight_group.gsight_acct.sfdc_acct_ownr as SFDC_Acct_ownr, sfdc_nagroup.vw_sfdcna_user.name,gsight_group.gsight_acct.work_space_creation_dt as GS_Work_space_creation_dt,sfdc_nagroup.account.d_u_n_s__c as SFDC_duns, sfdc_nagroup.account.subscriber_number__c as SFDC_Subscriber_Id, sfdc_nagroup.account.accountnumber as SFDC_Acct, sfdc_nagroup.account.id as SFDC_Account_Id, sfdc_nagroup.account.apts_isaddress_validated__c, sfdc_nagroup.account.apts_transferred_to_erp__cFROM gsight_group.gsight_acct inner JOIN sfdc_nagroup.account ON gsight_group.gsight_acct.duns = sfdc_nagroup.account.d_u_n_s__cleft join sfdc_nagroup.vw_sfdcna_user ON gsight_group.gsight_acct.sfdc_acct_ownr = sfdc_nagroup.vw_sfdcna_user.idlimit 1000 

    security_lion
    security_lionHelper ⭐️⭐️

    Allow members to block creepers, trolls, and spammersOpen

    Picture this: It’s the holiday and your team is taking a much deserved break. The rest of the organization is for the most part also enjoying this break. Unbeknowst to you, McCreepy Doomsday is sending innapropriate messages to your unsuspecting members. Your members ignore the messages, flag the messages, but the messages from McCreepy Doomsday keep coming and they’re escalating. Your members are now trying to reach your community managers, but everyone is out on holiday. Your community member feels unsafe. So unsafe, they take to social media and start trashing the community and company. No one is responding on social because your team is out.When you come back from vacation, you see the damage and reach out to the community member. Unfortunately, they’ve lost faith in you and the community and have vowed to never return. The problem: Members can’t report spam directly from messages or block members. The community member who is being harrased has to change their experience on the community: they can allow messages from everyone, only connections, or no one. Not only does the member suffer by being harrased, but now they have to change their experience because of a troll. The solution: Allow members to block/unblock other community members. They must first flag them (so a report is available to moderators) or go through a confirmation process and then they have the option to block the member. The moderator must have visibility into flagged and blocked users. The member must have visibility into who they have blocked and the option to edit that list. This might not be a problem while your community is small. You have a handle of your moderation plan and are almost always staffed. This is one of those safety issues you want to be preventive over reactive.