topic Pro Flo Tut 4 sec 4.4 Invalid destination at move object in FlexSim Forum

Pro Flo Tut 4 sec 4.4 Invalid destination at move object

tam_p — Mon, 19 Nov 2018 22:36:49 GMT

I am getting this error.

time: 229.369036 exception: Error: Invalid destination at move object activity "Move Object: Into Model" in "Sticker Roll Logic"

I have what the tutorial shows. How can I fix this?mistake-note.jpg proflowtut4atmpt2.fsm

Re: Pro Flo Tut 4 sec 4.4 Invalid destination at move object

joshua_s — Mon, 19 Nov 2018 22:53:40 GMT

Use up(current) instead in the Destination field, current.up worked on older versions.

Re: Pro Flo Tut 4 sec 4.4 Invalid destination at move object

tam_p — Mon, 19 Nov 2018 23:16:30 GMT

That seems to fix the problem. Thanks a million. Will you be fixing the tutorial for future users to not have to encounter that? Thanks. I am glad I finally got it to work.

Re: Pro Flo Tut 4 sec 4.4 Invalid destination at move object

joshua_s — Mon, 19 Nov 2018 23:19:11 GMT

Yes, we are compiling a list of things that need to be changed in the manual as new versions come out.

Re: Pro Flo Tut 4 sec 4.4 Invalid destination at move object

SCHamoen — Tue, 20 Nov 2018 08:07:16 GMT

@Joshua S This answer confuses me a bit, because the dot notation has come to Flexsim since version 2016 or something and the up(current) was always there. So are we going back from current.up to up(current)?

Re: Pro Flo Tut 4 sec 4.4 Invalid destination at move object

joshua_s — Mon, 26 Nov 2018 23:38:50 GMT

@steven.hamoen

This confused me to so I played around with it a little and found out that there was something going wrong with the referencing the first time current.up was put in. removing it, running it, even if errors pop up, restarting it then putting current.up in fixed it. current.up is fine, just something weird with some sticky referencing going on with this model.

Re: Pro Flo Tut 4 sec 4.4 Invalid destination at move object

Matthew_Gillespie — Mon, 26 Nov 2018 23:51:11 GMT

No, current.up is newer and correct. There was a bug that made properties on current look for a label instead of the property (i.e. current.up was looking for an "up" label on current). This bug has been fixed and there's no need to use the up() command.

@Joshua S, your answer is incorrect. There are no older versions where current.up worked and up(current) would not.