Codeless: Request object property not saving

Server Code
1

I’ve been doing some more testing with codeless, and I think I hit a bug with the “Get Request Object Property” block when creating an event:

For example, I selected that block, plugged it into my logic, and selected the “Street_Address” parameter that I want, from the drop down list of available options.
http://support.backendless.com/public/attachments/d4670f713a70c00791aef1dc75792322.PNG</img>
We can also see that the code reflects this:
http://support.backendless.com/public/attachments/f14ddd7858ce3232d4ed2795586cf3e4.PNG</img>

Now when I save or deploy (both display the same behavior) and then come back into the codeless editor again, the block resets to the default “ownerId” attribute and the code also reflects that.
http://support.backendless.com/public/attachments/3902c3c113f4b6cc8f6fca9b4e57f1c7.PNG</img>

Renato

d4670f713a70c00791aef1dc75792322.PNG

f14ddd7858ce3232d4ed2795586cf3e4.PNG

3902c3c113f4b6cc8f6fca9b4e57f1c7.PNG

2

Hi Renato,

When you say “then come back into the codeless editor again”, what were the steps after you saved/deployed your event handler and before you came back there?

Regards,
Mark

3

I tried a few workflows:

Scenario A

  1. Modify Logic
  2. Save / Deploy
  3. Move to somewhere else in console (say, by clicking data icon to navigate to my data tables)
  4. Click BL in sidebar, navigate back to the same event
  5. Observe that it’s reset

Scenario B

  1. Modify Logic
  2. Save / Deploy
  3. Click into any other service / event in the explorer (right hand folder menu in the codeless designer)
  4. Click back to my same event, in the codelss designer explorer
  5. Observe that it’s also reset

In the meantime, I was able to get the code to commit by using this workaround:
http://support.backendless.com/public/attachments/66954cb22ba7cedb1e6dc280a3831a34.PNG</img>

66954cb22ba7cedb1e6dc280a3831a34.PNG

4

Thanks, Renato. I was able to reproduce the problem. We will get it fixed asap.

Regards,
Mark

5

Thank you guys!

6

Hi Renato

We’ve fixed the problem and we will release it asap

Regards, Vlad

7

Hi Renato

We’ve released the fix just now

Regards, Vlad