New Bug Encountered:Very obscure syntax issue

[1minManager]

Tried to get the following to work in a template workflow -

<<SUM(Select([Related Materials [Job]][Custom.Invoice],[Custom Item]=TRUE))+SUM(Select([Related Materials [Job]][TOTAL Sale Price],[Custom Item]=FALSE))>>

I wouldn’t work. Issue was that it wouldn’t see [Related Materials [Job]] as a valid column name. When “Related Materials [Job]” is the exact name of the LIST column that shows related daughter records.

Tried SUM(Select([Related Materials [Job]][Custom.Invoice],TRUE)) in a virtual column to test and it failed too. But as I was messing about with it, for some reason

[Related Materials [Job]][Custom.Invoice] is invalid, yet

[Related Materials [Job]]
[Custom.Invoice] is valid

Seems a carriage return makes all the difference in a VC . In the end I renamed it to [Related Materials], but just though you might want to put this on a list of minor bug fixes.

[MultiTech]

Just as a matter of note, special characters should not be included in table or column names.

I would rename “Related Materials [Job]” to: Job_Materials

And “Customer.Invoice” I would rename to Customer_Invoice

[1minManager]

Hi Matt

it’s an App I’ve not really touched in 18months or so. I think that was the old naming convention? But I appreciate your point on the decimal point on column names

Simon

[Steve]

1minManager:

it’s an App I’ve not really touched in 18months or so.

Does the app use the [...][...] dereference construct successfully elsewhere?

[MultiTech]

Steve:

[...][...]

“reverse reference” is what I’ve heard Praveen call this. Like: [Related Records][Order Total]

Dereference: [Column].[Column] <— notice the dot… IT"S THE ONLY DIFFERENCE!!! (^_^)

[Steve]

MultiTech_Visions:

“reverse reference” is what I’ve heard Praveen call this. Like: [Related Records][Order Total]

That name doesn’t make much sense as nothing is being reversed. It’s more of a bulk dereference. It would be nice to have an official name for it…

[1minManager]

Yes the defref works fine in other sections which dont have square brackets in the name

[Steve]

I would guess, then, that this is a limitation in the expression parser. I would encourage you remove square brackets from column names.

[Phil]

We parse expressions using the EPPlus Excel parser.
Square brackets in a field name can confuse the EPPlus parser.

At one time, we used square brackets when generating the default Reverse Reference name.
We eliminated the square brackets in the default Reverse Reference name for exactly this reason.
If you have square brackets in a Reverse Reference field name and you want to use the field name in an expression, I recommend renaming the Reverse Reference field to eliminate the square brackets.