Is there somthing wrong with EVALUATE...?

voodoo

Hi, I have some problem with this part of my code:

   IF EVALUATE(StatusValue,ValueArray[1]) THEN BEGIN
      SETRANGE(Status,StatusValue);
   END

StatusValue is global variable, type Option;
ValueArray is type of text
Something is wrong with EVALUATE, because if I put only EVALUATE(StatusValue,ValueArray[1]) I have a messagebox:
You cannot enter 'Status::Released' in Option.

:-k

Thnx

kine

And which value you have in the ValueArray[1]?

voodoo

Like I said: Status::Released
It's the value from the field of my table UserFilter(field type is Text)

Thnx

Marije_Brummel

Have you tried setfilter instead of setrange?

Setrange expects the same datatype as the field, setfilter accepts strings.

You might have to remove the Status:: from the string.

kine

Mark Brummel wrote:

You might have to remove the Status:: from the string.

This is the source of the problems... :-)

And do not forget, that you will have problems when you switch your language...

DenSter

To elaborate...

You are right in using EVALUATE for this purpose, but you're going about it incorrectly. Syntax like 'Status::Released' is the C/AL code way to designate an option value. Internally, the database stores it as an integer (so you could even just set the filter on the integer value if you know which value that is). The text representation of the option value is just the word that belogns to the option, in your case that would be 'Released'.

So, try setting your array value to 'Released' and see if that works.

voodoo

Mark Brummel wrote:

Have you tried setfilter instead of setrange?

Setrange expects the same datatype as the field, setfilter accepts strings.

You might have to remove the Status:: from the string.

Problem is EVALUATE not setfilter or setrange, and I tried to remove Status:: from the string and I got the same message.

Marije_Brummel

The EVALUATE function is created to do things no other statement can do and basicly acts as if a user enters a field.

I don't think you have to use the evaluate function in this case. If the string in the user setup table is correct you should only have to make something like

SETFILTER(Optionfield, UserSetup.Optiontext);

Just make sure the text value in the usersetup has the right syntax.

voodoo

Mark Brummel wrote:

The EVALUATE function is created to do things no other statement can do and basicly acts as if a user enters a field.

I don't think you have to use the evaluate function in this case. If the string in the user setup table is correct you should only have to make something like

SETFILTER(Optionfield, UserSetup.Optiontext);

Just make sure the text value in the usersetup has the right syntax.

OK, let me explain, in Sales Header table, Status field is type of Option, and if I want to do this:
SETFILTER(Status, MyTable.Optiontext);
I will get an error in compile time: Type conversion is not possible because...
Option := Text
and I must do EVALUATE, right!?

misha

Marije_Brummel

Using SETFILTER you can use a string to set the filter, even if the table field has another datatype.

I think you are getting SETFILTER and SETRANGE mixed up :?

Have you tried it??

Make a small test:

SalesHdr.SETFILTER("Document Type", 'Order');
form.run(0, SalesHdr);

voodoo

Mark, thnx it's working :oops:
But, another problem is when I switch between languages, because, optionstring is text and it's value depend from chosen laguage........example:
Status::Released (in english) <-> Status::Lansiran (in serbian)

Marije_Brummel

Yes, this is the general problem with these type of filtering.

A workaround can be to work with numbers or to just write some more code.

You can also replace the text field in the user settings by an option string.

Do you want to filter on one option only or do you want to set multiple filters like "Quote|Order"??

DenSter

Try this:

SalesHeader.SETFILTER(Status,'=%1',MyTable.Optiontext);

DenSter

sheesh you guys are posting faster than I can type...

Marije_Brummel

That is because we use CodeGenius 8)

DenSter

That is advertising, did you pay your sponsorship dues to Luc? [-X

Marije_Brummel

Sssh :-$

DenSter

I won't tell anybody O:)

Marije_Brummel

8-[

DenSter

I just want to have the last word :-s

Marije_Brummel

I know 8)

Go right ahead.

voodoo

Mark Brummel wrote:

Yes, this is the general problem with these type of filtering.

A workaround can be to work with numbers or to just write some more code.

You can also replace the text field in the user settings by an option string.

Do you want to filter on one option only or do you want to set multiple filters like "Quote|Order"??

One option only....

Marije_Brummel

In this case you can also change your text filter in the user setup to an option field, then you won't have problems with the multilanguage thing.

Sorry for highjacking your topic :oops: