1. Feedback
  2. Angular
  3. 18512

Welcome to the Angular feedback portal. We’re happy you’re here! If you have feedback on how to improve the Angular, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Changing data set does not reset list of fields in Pivot Field List control

After resolving the issue from this forum post and support ticket, a new issue has been introduced:

https://www.syncfusion.com/forums/157261/pivot-field-list-not-clearing-fields-when-data-source-changed-to-have-no-data

https://www.syncfusion.com/feedback/17373/issue-in-component-refresh-with-empty-data-source

While the stated issue with clearing the data source associated with the pivot view has been resolved, there is a new unwanted behavior.

If I change the data source to a new, non-empty data set, the Pivot Field List continues to show the first loaded data set's list of fields.

- Clearing the data set does remove all the fields, but then changing to a non-empty data source still shows the first data source's fields, so clearing them does not resolve the issue.

- It does not matter how many times the data source is changed, it will always shows the initial data source's fields.

- The actual data source does seem to have changed, because placing the old fields into the rows/columns of the grid does not show any actual data, although the row and column headers do show the values from the initial data set.

NOTE: we use only dynamic data sets and do not specify the field list ahead of time.

I have verified that reverting the @syncfusion/ej2-angular-pivotview package to 18.2.57 resolves the issue, so this was definitely introduced in 18.2.58.

The control is basically unusable for us in its current state as our application is designed around changing and creating custom data sets. For now we can continue to use 18.2.57, but a quick resolution to this would be appreciated.


Thanks,

Michael