Implicit filter get applied during export on a highlighted row, results in partial export to csv
search cancel

Implicit filter get applied during export on a highlighted row, results in partial export to csv

book

Article ID: 263947

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

Implicit filter get applied during export when a user had a selection on an investment name and doesn't export all data of Grid.

Steps to Reproduce: 

  1. Create Hierarchy 
  2. Add few projects 
  3. Navigate to risks or status report modules
  4. Make sure we have more than records in grids from different projects
  5. Select a Project row
  6. Export to CSV
  7. The exported CSV will be only having data from the highlighted row of project and not all the data shown in the Grid

With above steps the data only belonging to that particular investment/project type are exported.

https://ci3.googleusercontent.com/proxy/ZdmCAZHznvfIHla8N6M4pwljnAIXj9Q96q2qNk2H0mi4a2U99CuSnHCWppjpQUgGaWDGeVxEBxtwIFuwVk2DelSApKckqZWra-t0xNZmhnCs0tGX7Q3XVEfR0ojwwFT5IG_k9oXtTk3gyjTWJDYZ7MS2OxHwDwrY4l-2aTe1iIeIs8087UmWAw=s0-d-e1-ft#https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=XP93snGkvCZWU8DeQVzz3A==     https://ci5.googleusercontent.com/proxy/pCAIfj9l5hJgT-AurDqZjMEq4d46Ed-qfjqlQQv9OS_nAlcYx5FqJlkqANn5ltAd6_DP37DAnedLRVjdwbGfUBXZyTawRn_MOwf5hSNF8cp68M6NhlMVPTIF6rr5S_BLcTtg-khfK9zFxp8gGffJseGQonV0SWeBbSPAG22kkxvNdTyREeNN4w=s0-d-e1-ft#https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=y7D/2Cp8ImFbNX9VCtU+bQ==

Expected Results: All the data shown on the grid should be exported as the user haven't applied any filtering.

Actual Results: Only data from highlighted project is exported.

Environment

Release : 16.1.1

Component: Clarity MUX UI Usability

Cause

It is a reported issue and tracked via DE69381.

Resolution

Workaround 

  • Deselect the highlighted row by refreshing page and just make an Export to CSV

The issue tracked as DE69381 is fixed in version 16.1.2

Additional Information

Related Articles