2899566 - Receiving "Invalid Group Detected" when editing permission groups

• A standard element was added in the dg-filter tag and it is causing the other filters to not work;
• When clicking under Active group Membership, under Manage permission group, the message below is being shown:
  
  • The filter specification of this group cannot be restored. This can be caused by a new data model or internal changes.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors HXM Suite

1. Export Data Model
2. Add any standard Element field inside the dg-filter.

Example

<dg-filters>
    <permission-group-filter>
      <standard-element-ref refid="custom01"/>
      <hris-element-ref refid="jobInfo">
        <hris-field-ref refid="job-code"/>
        <hris-field-ref refid="employee-class"/>
        <hris-field-ref refid="department"/>
        <hris-field-ref refid="division"/>
      ...


               3. Save data model
               4. Go to Admin center -> manage permission groups -> select any permission group -> no users are listed
               5. if you click on the active members, you get pop "invalid group detected"

"The filter specification of this group cannot be restored. This can be caused by a new data model or internal changes.Please delete this group and re-create it."

There is only one standard element in '<permission-group-filter>' under '<dg-filters>': it is 'custom01'. Only this filter will work in dynamic filter.

When you define only this standard element, then this specific standard element will be the only available standard filter in dynamic group filter. Any groups defined with other default filters but not 'custom01' before will not work any longer.

• Delete this line "<standard-element-ref refid="custom01"/>" in '<permission-group-filter>' under '<dg-filters>'. Then, re-import the data model. This will make the default standard filters to work.

• If in the event that you need to add a standard element in dg-filter, create a new tag and close the element using </my-filter> tag

Example:

<dg-filter>

  <my-filter>

     <standard-element-ref refid="custom01"/>

 </my-filter>�

Note: This applies to other custom fields also, the above has been provided as an example. 

Note: For CPS please see internal memo

Important Note:

permission-group-filter can be Export from Master data model

• Export master data model from : 3153500 - How to Download Data Models, Picklists and other configuration files for Employee Central - SuccessFactors

Or

• The Master Data Model can be found here: https://help.sap.com/doc/180ae8b64b4e43c68e975ab9be597aa7/latest/en-US/EC-Master_Data_Models.zip

 Example:

 <!--

    To enable keyword search on data elements, make sure that read permissions are enabled for all roles.

  -->

  <dg-filters>

    <permission-group-filter>

      <hris-element-ref refid="jobInfo" extend-by-n-days="90">

        <hris-field-ref refid="business-unit"/>

        <hris-field-ref refid="cost-center"/>

        <hris-field-ref refid="company"/>

        <hris-field-ref refid="pay-grade"/>

        <hris-field-ref refid="job-code"/>

        <hris-field-ref refid="employee-class"/>

        <hris-field-ref refid="location"/>

        <hris-field-ref refid="department"/>

        <hris-field-ref refid="division"/>

        <hris-field-ref refid="company" ref-field="countryOfRegistration"/>

        <hris-field-ref refid="location" ref-field="locationGroup"/>

        <hris-field-ref refid="department" ref-field="name"/>        

      </hris-element-ref>

      <hris-element-ref refid="compInfo" extend-by-n-days="120">

        <hris-field-ref refid="pay-group"/>

      </hris-element-ref>

    </permission-group-filter>

  </dg-filters>

Also

When there is no "standard-element-ref" tag configured in succession data model under "permission-group-filter" tag. If there is at least one "standard-element-ref" tag available then it checks if it valid(the ones in above documentation) then display it in Dynamic groups dropdown.

 under dynamic group dropdown in "Manage Workflow Groups" and will also be able to open existing groups.
View : How Do You Specify Which Fields to Use?

If you don’t specify any fields in the <dg-filters> XML configuration, then RBP defaults to display all of the possible fields listed in Standard Fields Available to Use as Filters in Permission Groups. By specifying the fields, you replace the standard filters with your own list. If you specify an unsupported field with <standard-element-ref>, the field doesn't display in the RBP Permission Groups UI.

Dynamic Groups dropdown shows all the standard element dg-filters which are mentioned in Standard Fields Available to Use as Filters in Permission Groups. 

Standard Fields Available to Use as Filters in Permission Groups

The fields that can be used when defining permission groups are the standard fields listed below, as well as any of the HRIS fields when Employee Central is enabled.

When there is no "standard-element-ref" tag configured in succession data model under "permission-group-filter" tag.

If there is at least one "standard-element-ref" tag available then it checks if it valid(the ones in above documentation) then display it in Dynamic groups dropdown.

FAQ - Additional Information

Q) Where can I get information on this from the Guide?

A) Guide: Implementing Role-Based Permissions

Chapter - Standard Fields Available to Use as Filters in Permission Groups

• 2591825 - Custom DG Filter
• 2847576 - How to add a DG Filter in "Manage Business Configuration" - Employee Central.
• 2880552 - How to add additional employee profile fields in Manage Business Configuration - Employee Profile
• 2236372 - Value not showing in RBP Permission Group - People Pool Category Search Filters List
• 2713520 - DG Filters not Showing in Manage Business Configuration

Invalid Group Detected, permission group, dg filter, standard element, custom, filters, invalid group detected, The filter specification of this group cannot be restored. This can be caused by a new data model or internal changes.Please delete this group and re-create it , KBA , LOD-SF-PLT-MNG , Manage user Issues , LOD-SF-EC-RBP , Roles & Permissions (EC Core only) , LOD-SF-RCM-ADM , Admin Center, RBP, Permissions and Settings , Problem