Dynamic code changing?

abartonicek · 2005-12-02

I know you all think that's impossible, but, Navison can do that too

I have this line of code:

PurchaseLine."Unit of Measure Code" := PurchaseLine."Unit of Measure Code"::KG;

and after I compile it and run it the line looks like this:

PurchaseLine."Unit of Measure Code" := PurchaseLine."Unit of Measure Code"::"4672511";

Any ideas?

Marije_Brummel · 2005-12-02

"Unit of measre code" if no optionfield but a codefield.

So the :: assignment is not allowed.

Try

PurchaseLine."Unit of Measure Code" := 'KG';

Marije_Brummel · 2005-12-02

See also

http://www.mibuso.com/forum/viewtopic.php?t=7563

DenSter · 2005-12-02

I'm surprised that compiled at all in the first place.

abartonicek · 2005-12-02

It's same as:

PurchaseLine."Document Type" := PurchaseLine."Document Type"::Invoice;

If I omit PurchaseLine and make it:

PurchaseLine."Document Type" := "Document Type"::Invoice;

I get compile error : Unknown variable "Document Type"

"Unit of Measure Code" is optionfield.
My code works well, but it gets altered

Code:

PurchaseLine."Unit of Measure Code" := 'KG';

works too.

Marije_Brummel · 2005-12-02

:?:

Did you change the datatype of field

5407 Unit of Measure Code Code 10

:-s

abartonicek · 2005-12-02

:oops:
I wrote it wrong (in code and in post), it's not option field.

I had 10 similar lines of code above that one so i guess I didn't think.

#-o

But still, how come the source changed?
The source

...option::"2"

after compile does not change to something like:

....option::SecondChoice

Or does it? :?:

Marije_Brummel · 2005-12-02

I think the compiler converts all fieldsnames tablenames and optionstrings to numbers.

That's probably why it accepts these numbers

Read this post

http://www.mibuso.com/forum/viewtopic.php?t=7563

Marije_Brummel · 2005-12-02

This is a nice Friday Afternoon topic =D>

:whistle:

abartonicek · 2005-12-02

No, I didn't mean that.

I did read the post and I understand that but I think that author of that post ment that

SalesLine.Type := SalesLine.Type::Item;

and

SalesLine.Type := SalesLine.Type::"2";

give same results.

But it doesn't mean that if I have CodeUnit with code

SalesLine.Type := SalesLine.Type::"2";

and when I do compile, save, close codeunit, open codeunit that that line will say:

SalesLine.Type := SalesLine.Type::Item;

True?

Marije_Brummel · 2005-12-02

You are right! :shock:

But that's what the author of the other post (me

) is trying to say!

Maybe I should have put it in other words :oops:

abartonicek · 2005-12-02

The important thing is that the AUTHOR knows the meaning

Well, it's the end of the week O:)
Sorry for telling you what you meant :-#

Marije_Brummel · 2005-12-02

Have a nice weekend

jm · 2005-12-02

Hi,

please have a look at:
http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=6096

br
Josef Metz

Marije_Brummel · 2005-12-02

Does not work in 4.00 :shock:

Guess the 'bug' is fixed =D>

kriki · 2005-12-05

Mark Brummel wrote:

I think the compiler converts all fieldsnames tablenames and optionstrings to numbers.

That's probably why it accepts these numbers

Not probably. It IS the reason.
Also option-fields, in reality, are integers.

Dynamic code changing?

Comments

Categories