topic Re: Using the P() function in App Development

Using the P() function

timetraveler — Tue, 22 Dec 2020 15:35:17 GMT

Hi,

The set expression editor is giving me an error when I try to use the P() function in this way:

sum({$ < FIELD_1 = {$1}, FIELD_2 = {$2}, Period = P($3) > } Amount)

I'm "calling" this like:

vFunction(A,B,Q1) , vFunction(A,B,Q2)...

So the third parameter $3 is changing, as it's a date. Q1 and Q2 are text(date#) format and
Period is a date format. So the expression does what I want, but it's giving me an error and I would like to write it properly.

Thank you

Re: Using the P() function

marcus_sommer — Wed, 23 Dec 2020 14:17:00 GMT

Are Q1 and Q2 fields within your datamodel? Further comparing real dates with strings will only work in some very specific cases and should be therefore in general avoided.

- Marcus

Re: Using the P() function

timetraveler — Wed, 23 Dec 2020 14:28:29 GMT

Hi, thanks for the reply, yes they are fields. I made them this text format while I was testing something. I can make them into a date again. The main point is that if I write:

Period = P(Q1),

there will be no error.

But if I write P($3), there is an error...

Re: Using the P() function

marcus_sommer — Wed, 23 Dec 2020 14:50:42 GMT

Try it in this way: vFunction(A,B,[Q1])

- Marcus

Re: Using the P() function

timetraveler — Wed, 23 Dec 2020 15:01:02 GMT

Hi, the call of the function (within a master item) is not causing an error. It's the function itself (where P($3)) . I tried with P([$3]) and all kinds of different brackets but I guess I didn't find the right one, or it's a bug in the expression checker itself.

Re: Using the P() function

marcus_sommer — Wed, 23 Dec 2020 15:12:21 GMT

If it's worked you could ignore the expression checker which is a good indicator but is independent from the executing engine and therefore not mandatory the truth.

- Marcus