Skip to main content
prashant_pareek
prashant_pareek
Contributor ⭐️
May 5, 2020
New Idea

Low volume object : Restrict fields that can be edited via Data operation or Related list in Customer 360

  • May 5, 2020
  • 2 replies
  • 75 views

From an Admin perspective it would be nice to restrict end users from editing some fields in a Low volume object while editing via Data operation or Related list in Customer 360 by making them Read only or not visible in the layout would be really helpful. Currently we need to designate that with the field names. These fields should be updated only by the admin for maintaining data quality. 

      2 replies

      pgeorge
      Gainsight Employee ⭐️
      pgeorge
      Gainsight Employee ⭐️
      June 9, 2020

      Hi @prashant_pareek 

       

      Thank you for the feedback

      We are working on bringing field-level permissions to Data models. It is currently on our mid term roadmap

       

      Thank you

      Preethi

        sdrostgainsightcom
        sdrostgainsightcom
        Gainsight Employee ⭐️⭐️⭐️
        March 9, 2021

        Any update on this? It’s critical for making this a truly useful, adoptable feature.

         

        Current use case for Gitlab:

        • LV object holds Instance information, including an Instance ID and Subscription ID that are the combination keys for updates of selected attributes by Rules Engine.
        • There is currently one field that they need their TAMs/CSMs updating on a regular basis.
        • At the moment, they can change any of the keys used by Rules Engine as upsert IDs by accident or because they are trying to “reparent” to a new subscriptions - leading to multiple records when the rule updates from source data.

        Hand in hand with setting fields as editable or not is displaying them on the View popup the way Person view popup works - unable to leave off fields that aren’t relevant to the 1-record view mode.

        Let us know - thank you!

        Scott Drost, Gainsight -- Principal Customer Success Architect
          Terms & ConditionsAccessibility statement