Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more

Added Timeline 2.4.0 slicer visual in report & giving rendering report error go to FOCUS MODE

Hi, I am using Time 2.4.0 slicer visual in my report for the time date hierarchies. and I have 7 pages in my one report and all of the pages have this timeline slicer in it.
The issue comes when I try to go to FOCUS MODE for this timeline  slicer - it's strange that in only one of the 7 pages, I am getting an error on that specific page only : 

Amber_Dogra_0-1670389961840.png

Adding More details for the error below:

 

Feedback Type:
Frown (Error)

Timestamp:
2022-12-07T05:03:51.7011519Z

Local Time:
2022-12-07T10:33:51.7011519+05:30

Session ID:
35608230-c572-4f87-a064-085f5b79d6c7

Release:
October 2022

Product Version:
2.110.1161.0 (22.10) (x64)

Stack Trace:
Javascript: TypeError
at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:298658:75
    at _proto37.insert (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:298668:22)
    at VisualContainerRepeatComponent.createVisualContainer (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:185924:39)
    at VisualContainerRepeatComponent.reloadCustomVisuals (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:185957:105)
    at VisualContainerRepeatComponent.relocateCanvasItemContainer (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:185941:75)
    at VisualContainerRepeatComponent.onPopOutModeChanged (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:185848:143)
    at Object.<anonymous> (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:185822:38)
    at Object.dispatch (https://ms-pbi.pbi.microsoft.com/minerva/scripts/jquery.js:5429:27)
    at elemData.handle (https://ms-pbi.pbi.microsoft.com/minerva/scripts/jquery.js:5233:28)
    at Object.trigger (https://ms-pbi.pbi.microsoft.com/minerva/scripts/jquery.js:8715:12)

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.110.1161.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js","Component":"","Error":"TypeError","MethodDef":"","ErrorOffset":"298658:75"}

OS Version:
Microsoft Windows NT 10.0.19044.0 (x64 en-US)

CLR Version:
4.8 or later [Release Number = 528372]

Peak Virtual Memory:
70.6 GB

Private Memory:
578 MB

Peak Working Set:
1.11 GB

IE Version:
11.789.19041.0

User ID:
96da9369-9ee4-4711-b54b-4b8f78d439ab

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

Model Default Mode:
Import

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_enableWebView2
PBI_sparklines

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_azureMapVisual
PBI_compositeModelsOverAS
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PQ_WebView2Connector
PBI_scorecardVisual
PBI_NlToDax
PBI_fieldParametersSuperSwitch
PBI_horizontalFusion
PBI_relationshipEditPane

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

Recent Actions:
VisualContainerPersistProperties

DPI Scale:
150%

Supported Services:
Power BI

 

 

Any early help would be really appreciated, thanks-in-advance!

Status: Needs Info

Hi @Amber_Dogra ,

 

Have you tried to update the power bi desktop to the latest version?

There was a user with the same error before that, and it was solved when he updated to the latest version. You can try to use the new version as well.

 

Best regards,

Community Support Team Selina zhu

Comments
v-mengzhu-msft
Community Support
Status changed to: Needs Info

Hi @Amber_Dogra ,

 

Have you tried to update the power bi desktop to the latest version?

There was a user with the same error before that, and it was solved when he updated to the latest version. You can try to use the new version as well.

 

Best regards,

Community Support Team Selina zhu

Amber_Dogra
Advocate I

Yes, Issue resolved once I've updated the visual version.
It's just needed the visual update!