Dynamic filter on indicator source is ignored while running data collectionIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview When a user has pa_admin role but not admin, using this user as 'Run as' for data collection job will ignore any dynamic filters on indicator source to filter elements. [Subject] Dynamic filter on indicator source is ignored while running data collection. Example When a script include is used to filter elements on indicator source facts table, the data collection job will ignore the dynamic filter and collects scores for all elements. This results in showing different count upon previewing indicator source compared to the score shown on scorecard/analytics hub after data collection is done. This may happen when the data collector is run as a pa_admin instead of admin. This is because a non-admin user with pa_admin role may have privileges to use all PA features but not all script includes are available for non-admin users. To resolve issues like this, always run data collection jobs as a valid admin user.