| View previous topic :: View next topic |
| Author |
Message |
sla Just can't stay away
Joined: 14 Jun 2007 Posts: 20
|
| Posted: Tue Aug 07, 2007 7:39 am Post subject: Error in the $$NULL function parsing (4.8.5) |
|
|
When designing and previewing my signature i have had several issues with the preview dialog complaining about "Invalid column name (JobTitle".
Notice the "(" in front of the field name indicating that the might be missing some ")" or a "(" to many!.
However there is no syntax error in the template where the line that produce this error is:
{$$NULL(JobTitle)$$VALUE(((JobTitle)))$$}
I experimentet with this a lot and found that simply changing the line to read:
{$$NULL(JobTitle)$$VALUE( ((JobTitle)) )$$}
Will eliminate the problem.
Conclusion:
There must be some kind of error in the template renderer.
Regards
Søren Lambæk
KPC Byg A/S |
|
| Back to top |
|
 |
Jesper Frier Certified Professional


Joined: 09 Sep 2006 Posts: 1940 Location: Stoevring, Denmark
|
| Posted: Tue Aug 07, 2007 9:07 am Post subject: Insert function |
|
|
Using version 4.8.6 Beta.
Clicked Insert function and get below code in my signature:
| Code: | | {$$NULL(Mobile_number)$$VALUE(Mobile: ((Mobile_number)) )$$} |
If I need another field to by dynamic, I simply replace Mobile_number with e.g. JobTitle.
Unfortunately, I cannot reproduce above code error ... nothing is changed from 4.8.5. |
|
| Back to top |
|
 |
sla Just can't stay away
Joined: 14 Jun 2007 Posts: 20
|
| Posted: Tue Aug 07, 2007 9:39 am Post subject: Re: Insert function |
|
|
| Jesper Frier wrote: | Using version 4.8.6 Beta.
Clicked Insert function and get below code in my signature:
| Code: | | {$$NULL(Mobile_number)$$VALUE(Mobile: ((Mobile_number)) )$$} |
If I need another field to by dynamic, I simply replace Mobile_number with e.g. JobTitle.
Unfortunately, I cannot reproduce above code error ... nothing is changed from 4.8.5. |
Please try changing your example to:
| Code: | | {$$NULL(Mobile_number)$$VALUE(((Mobile_number)))$$} |
I think your parser might have difficulties decoding the three "(((" after the VALUE keyword. I guess it breaks it into these components:
VALUE : keyword
(( : start of a fieldname
(Mobile_number : fieldname which is wrong
)) : end of fieldname.
Regards
Søren Lambæk
KPC Byg |
|
| Back to top |
|
 |
Jesper Frier Certified Professional


Joined: 09 Sep 2006 Posts: 1940 Location: Stoevring, Denmark
|
| Posted: Tue Aug 07, 2007 12:27 pm Post subject: |
|
|
OK - I understand.
We will try to find a way so that the code works after manuel editing where 'Mobile:_' is removed:
| Code: | | {$$NULL(Mobile_number)$$VALUE(((Mobile_number)))$$} |
Thank you for your input. |
|
| Back to top |
|
 |
Bjarne Mess Certified Professional


Joined: 01 May 2007 Posts: 735 Location: Copenhagen
|
| Posted: Thu Aug 09, 2007 6:35 am Post subject: |
|
|
True, there cannot be a ((( in the function. Please write it as ( ((, where (( denotes the dynamic field. sign.exe will automatically remove leading blanks.
This is how it is designedand parsed. _________________ </Bjarne> | Test Email Signature | Showcase |  |
|
| Back to top |
|
 |
Jesper Frier Certified Professional


Joined: 09 Sep 2006 Posts: 1940 Location: Stoevring, Denmark
|
|
| Back to top |
|
 |
sla Just can't stay away
Joined: 14 Jun 2007 Posts: 20
|
| Posted: Thu Aug 09, 2007 7:49 am Post subject: |
|
|
How was i supposed to know that? It took me several ours of trial and error testing to figure this out by my self.
And when your examples say that:
| Code: | | {$$NULL(Mobile_number)$$VALUE(Mobile: ((Mobile_number)) )$$} |
Gives:
Without a space in front of "Mobile:" The user ( ME! ) naturaly expects that if I want the output to to bee just:
Without a leading space! then i should write:
| Code: | | {$$NULL(Mobile_number)$$VALUE(((Mobile_number)))$$} |
You need either to change the parsing of the function or introduce a real syntax checking engine which will help the signature designer figure out what is wrong with the function statement's.
Regards
Søren Lambæk
KPC Byg a/s |
|
| Back to top |
|
 |
Bjarne Mess Certified Professional


Joined: 01 May 2007 Posts: 735 Location: Copenhagen
|
| Posted: Mon Aug 13, 2007 10:13 pm Post subject: |
|
|
Thank you for good input. The parser will be improved.
In the next version of eMailSignature the Cockpit will take care of possible syntax errors in the email signature functions so you will not experience issues due to syntax error anymore. _________________ </Bjarne> | Test Email Signature | Showcase |  |
|
| Back to top |
|
 |
|