cannot pass Global Table node to 'query' command

Question

question

Will Bishop asked Sep 24 2016 at 12:51 AM BenJoaquin Gouverneur commented Sep 27 2016 at 11:12 PM

cannot pass Global Table node to 'query' command

Ahoy! I am using the query() command a lot to access Global Table data, and I love the $ syntax for building parameterized queries. However, it seems like I can only pass in a parameterized table via reftable(). If I try to pass in a treenode of a Global Table or a Global Variable pointing to a Global Table, I get an error. This is confusing, since I thought that reftable() was a node reference. See below for my example code querying a "sample_table".

I'd like to be able to save my table to something like a global variable to make updating it easy/centralized; I could do this with reftable() and a Global Macro for table-name, but a node reference would ideally be a faster.

This parameterized query works fine:

query("SELECT * FROM $1 WHERE PART_NUMBER = 'E'", reftable("sample_table"));
int rows = getquerymatchcount();
if (rows > 0) {
	string res = getqueryvalue(1, "MATERIAL_LOC");
	pt(res);
} else {
	pt("no matches");
}

This query with a table node reference doesn't work.

query("SELECT * FROM $1 WHERE PART_NUMBER = 'E'", 
	node("Tools/GlobalTables/sample_table", model()));
int rows = getquerymatchcount();
if (rows > 0) {
	string res = getqueryvalue(1, "MATERIAL_LOC");
	pt(res);
} else {
	pt("no matches");
}

This surprisingly also doesn't work if I pass in a Global Variable set to reftable("sample_table").

Software Version:

FlexSim 16.2.0

user command

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2016-09-24T05:33:18Z

Matthew Gillespie answered Sep 24 2016 at 5:33 AM BenJoaquin Gouverneur commented Sep 27 2016 at 11:12 PM

The actual table of a global table is stored on the "data" variable of the Global Table object. If you put your reftable() command in the script console and execute it you'll see the full path.

· 4

Will Bishop commented · Sep 26 2016 at 3:52 PM

Thanks @Matthew Gillespie -- the reftable call does point to the variable/data path you describe (shown below).

reftable("sample_table") --> MODEL:/Tools/GlobalTables/sample_table>variables/data

When I set a Global Variable to this treenode (the ...table>variables/data), then passing the Global Variable to the query works. Thanks!

1 ·

BenJoaquin Gouverneur commented · Sep 27 2016 at 9:38 PM

@Matthew Gillespie, I'm confused why I can't pass a Global Variable set to reftable("sample_table") into a query. As @Will Bishop mentions, it doesn't work. Please explain why.

Thanks.

0 ·

Matthew Gillespie ♦♦ BenJoaquin Gouverneur commented · Sep 27 2016 at 9:56 PM

It's working fine for me. Check out this sample model.

Are you trying to put the reftable command in the Value field of the global variable? That's not a code field, the code will never get evaluated.

1 ·

globaltable-globalvar.fsm (13.3 KiB)

BenJoaquin Gouverneur Matthew Gillespie ♦♦ commented · Sep 27 2016 at 11:12 PM

Yes @Matthew Gillespie, I was putting the command in the value field. Instead I'll assign the global variable in a script with gv_table = reftable("sample_table");.

Thanks for the help!

0 ·

question