ThingWorx Environment Crashes From Data Export Widget

[JK_10744682]

Hi all,

My team experienced a system crash today after using the Data Export widget. We believe that a spam click of the data export caused the crash so I am looking for a way to prevent a user from multi-clicking the export widget if it is slow to export. Any ideas on a good way to prevent multi clicking of the widget?

[Bikash_Panda]

On click you may disable the export button and reenable only after service invoke is complete for the export.

[JK_10744682]

The Data Export button does not have an OnClick action or disable property and also doesn't have a service invoke complete action. The only properties that are bindable are shown below.

[Rocko · Accepted solution]

1) FYI: Data Export widget is legacy in TWX 9.7 and replaced with an expression instead.

2) on your problem:

Make the datexport widget invisible. Create your own button. Bind button onClick to Export Service of dataexport widget.

Make button also inactive on Onclick via binding it to an expression.

Neither dataexport widget nor dataexport expression support an "Export Completed" event, so you might have to use a timer with a reasonable amount to trigger reenabling your export button.

3) I am sceptical the data export widget can cause a system crash. Eventually you might want to reevaluate your investigation.

[nmutter]

regarding 3) I would also not have thought so but interestingly when exporting - the widget initiates a call to the source service for it's data with "Accept: text/csv". Depending on the complexity of this service I see platform might crash.

Really interesting how this widget itself calls the service again whose data is bound to it. Maybe with 9.7 the behavior will change for the 'widget'.

[abandal]

Hi @JK_10744682,

I wanted to follow up with you on your post to see if your question has been answered.
If so, please mark the appropriate reply as the Accepted Solution for the benefit of other members who may have the same question.
Of course, if you have more to share on your issue, please let the Community know so that we can continue to support.
 

Thanks,
Abhi