Accessing customtable data from within a macro (Kentico v7)

You doing everything right except the system doesn't how many rows you are going to get after "where":

{% GlobalObjects.CustomTables["customtable.SampleTable"].Items.Where("ItemID = 1")[0]["EmailText"] |(identity)GlobalAdministrator%}

ie. where("condition")[0]["fieldname"]

Still no luck unfortunately, I've been trying a few different permutations. The items value always appears to be null.

"where" returns array with 1 item! i.e. you do [0] not [1]

You have to do .Items.Where("ItemID=1")[0]["EmailAddress"]

Still null. Shouldn't the Items debug value is something non-null?

You probably misspelled table name. My code in the first comment is working. Try .Items.Count to see if you have anything in the table. If you just do: {%GlobalObjects.CustomTables["customtable.sampletable"].Items|(identity)GlobalAdministrator%} you should get some output if the table is not empty

Hmm. If I change name of table to something I know that is incorrect, it correctly returns null

I've tried Items.Count (and Length) but they both return null. The customtable is available to the site and the permissions look okay.

Not sure if this is possible in Kentico v7.

I think you are getting the name of the table wrong. Is it a real custom table in Kentico? You should use codename i.e. All those macros

do return somehting:

P.S. Make sure that this a custom table in SQL i.e.:

I think you just trying access some table in your DB , but it it not a customtable in Kentico sense.

If you want to access form table it will be a different macro: dont remember how it was in 7 but this will work in 11: {% GlobalObjects.BizForms["BizForm.TestForm"].Items.Count |(identity)GlobalAdministrator%}

I can access the table name but not the items. Very strange.

And the data in the sample table:

You've got to play with macros, there was macro tester I used to use, but you can do in the interface as well. Here you have access to macros

Get to custom tables I don't think .Items exist in 7. It has to be a way around it. In the worst case scenario you can create a custom macro and access data via API, but play around it has to be something there.