Idea

Jon Abbott avatar image
7 Likes"
Jon Abbott suggested

Make Table reference error text more descriptive

When I use the Table command to access a Global Table, and I enter in a table name that doesn't exist, the table name doesn't show in the error message. Here is the current error message text for when I try to reference a non-existent "GlobalTable2" using Table:

exception: FlexScript exception: Row 1 is not a valid row name for <no path> at /0 c: /testlink_instance i: /testlink_associated

For debugging large models, it would be more useful if the error message mentioned the table name that it could not find, like the following:

exception: FlexScript exception: Table "GlobalTable2" is not a valid table name

We use a lot of table lookups in our models, so having this kind of error message output would make it much easier to trace down the issue when a table name doesn't match. Another idea to augment this would be to include the name of the object that the erroneous Table call came from. Thanks for considering implementing these ideas.

error messagedebuggingflexsim 201818.0.3verbosity
5 |100000

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

No Comments

·

Write a Comment

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

Your Opinion Counts

Share your great idea, or help out by voting for other people's ideas.