Forum Discussion
Display function creates fabric error widget_id (f9aa9357-73c1-44dc-a51c-f15158fa97bf) not found.
Hi,
Went back working of my Python code in one of my Notebooks and what the hell... display() function does not work anymore. I'm getting this error "widget_id (f9aa9357-73c1-44dc-a51c-f15158fa97bf) not found". WTF... what about reliability with MS Fabric!!!.
Does anyone know more about this ?
Tx,
JR
Hello JRGuilbault I was not expecting a Kudos from my message - the last line on my message is just a signature that gets added as default - apologies if that caused any confusion.
In regards to your issue, it is indeed something that several others are facing, starting today. I tried it myself and I get the same experience as you. There is an active issue logged for this on the "Known Issues" portal. Here's a link.
Unfortunately there's no workaround for this at this point in time, so you'd have to live with df.show() for the time being instead of the display() function. Hopefully Microsoft will fix it soon. The page says "Engineers are investigating the issue and an update will be provided soon"
7 Replies
- deborshi_nag
Super User
Hello JRGuilbault
The display function renders 1000 rows of the dataframe by default. If your dataframe in question is a wide or a heavy dataframe it may disrupt the rendering. Can you try restricting it to a limited number of rows?
display(df.limit(1000))ordf.show(20, truncate=False)It could also be a session connection or a temporary rendering hiccup.Hi,
Thank you for your quick reponse... I am a advanced Fabric user... You can trust that the rendering limit of 1000 does not merite a kudos and surely is not solving the issue !!!! But please receive my warm thank you for your help. This issue is completely preventing me from working today!!!
My regards!
- deborshi_nag
Hello JRGuilbault I was not expecting a Kudos from my message - the last line on my message is just a signature that gets added as default - apologies if that caused any confusion.
In regards to your issue, it is indeed something that several others are facing, starting today. I tried it myself and I get the same experience as you. There is an active issue logged for this on the "Known Issues" portal. Here's a link.
Unfortunately there's no workaround for this at this point in time, so you'd have to live with df.show() for the time being instead of the display() function. Hopefully Microsoft will fix it soon. The page says "Engineers are investigating the issue and an update will be provided soon"
Try this...
import numpy as npimport pandas as pdData_dic = {'A': [1, 2],'B':[2, 10]}Data_df = pd.DataFrame(Data_dic)print("Using 'print' function to output Dataframe")print(Data_df)print("\nUsing 'display' function to output Dataframe")display(Data_df)Data_spark = spark.createDataFrame(Data_df, schema=Data_df.columns.to_list())print("\nUsing 'print' function to output Dataframe")print(Data_spark)- deborshi_nag
Thank you for supplying the code - it helped me try this myself and identify the open issue with Microsoft!
This is what I am getting
Using 'print' function to output Dataframe
A B
0 1 2
1 2 10Using 'display' function to output Dataframe
Using 'print' function to output Dataframe
DataFrame[A: bigint, B: bigint]
