Good day to you.
This a known issue in the latest version 17.1.44
. The fix for this issue will be included in the upcoming Volume 1 SP1 release which is expected in the mid of May 2019. You can now track the current status of the report, review the proposed resolution timeline, and contact us for any further inquiries through this link: https://www.syncfusion.com/feedback/6231/
Meanwhile, you can use the version 17.1.43 to get this issue resolved in your end, until the fix is available.