On domain-separated instances, Performance Analytics Collection jobs do not use [sys_choice] Breakdown Elements defined on a parent domain only. As a result, scores are not collected per Breakdown Element.
Steps to Reproduce
Activate the Performance Analytics - Premium plugin [com.snc.pa.premium] and Domain Support - Domain Extensions Installer plugin [com.glide.domain.msp_extensions.installer].
Establish a domain structure with a parent and a child domain.
For more information, see the product documentation topic Domain separation.
Establish a Performance Analytics user on the child domain.
Create new State choices, for example, for [sc_req_item.task] on the parent domain only. Similar choices exists in global. Do the same thing for [task.state].
Create a few Requested Items (in this example) on the child domain.
Establish the following Performance Analytics setup in the global domain:
- Breakdown Source based on the [sys_choice] table with active records only for [sc_req_item.state]
- Breakdown mapped to [sc_req_item.state] (in this example)
- Indicator Source and Indicator based on the [sc_req_item] table (in this example)
- Collection Job with Run As the newly created user
Run the Collection Job.
Expected result: Scores are recorded per Breakdown Element using the choices defined on the parent domain because there are no choices on the child domain.
Actual result: The score's element column is empty. In the database, the Element column shows "unmatched."
This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.
Related Problem: PRB1252332