question

Sachin N avatar image
0 Likes"
Sachin N asked Sachin N answered

Chart template error on reset

I am getting the following error on resetting the simulation. I am able to create the chart for state tracking and run. On further reset the chart does not display anything with the following error...I am not using the staff function at all as most of the simulation is in process flow

exception: Exception Caught in ObjectFunction400__project_library_statistics_ChartTemplate_behavior_eventfunctions_onPostSave object: /Tools/PeopleTables/StaffAvailability class: MAIN:/project/library/statistics/ChartTemplate exception: Exception caught in TreeNode::callMemberFunction() c++/dll execution. Throwing...

MAIN:/project/library/statistics/ChartTemplate>behavior/eventfunctions/onPostSave c: /Tools/PeopleTables/StaffAvailability thisClass: MAIN:/project/library/statistics/ChartTemplate exception: FlexScript exception: VIEW:/nodefunctions/savemodelrestore

FlexSim 20.0.2
chart template error
· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Brittany Evans avatar image Brittany Evans ♦ commented ·

Is there any chance that you could send us the model so we can try to better see what could be causing the issue?

0 Likes 0 ·

1 Answer

Sachin N avatar image
0 Likes"
Sachin N answered

Thank you for your answer, I was wondering if you could tell what was wrong quickly looking at the error. It will be quite some work for me to recreate the issue on a model I can share...meanwhile I went back to an earlier version of the model before the errors started showing up and kind of developed a workaround. For now this is holding!

· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Ben Wilson avatar image Ben Wilson ♦♦ commented ·

Hi @Sachin N,

The errors seem to be coming from chart templates (ChartTemplate is mentioned in the node path for the exception), so perhaps there was an error with a chart you were trying to display.

Glad you found a work around!

0 Likes 0 ·