Yurii Orishchuk
Posts: 0
Joined: Fri Feb 14, 2014 8:20 am

New Interface: Generated Transactions Not Matching Mapping Upgrade

HI Joseph,

Thanks for your description to reproduce this problem.

This time i've been able to reproduce it.

I've tried to:
pre

1 Save project backup.
2 Restore app(with other name for start) from this backup.
3 After restoring it works new app.

/pre

I guess problem could be in source editing.

Please try this solution and let us know about results here.

Regards.

Joseph Francis
Posts: 0
Joined: Thu Sep 04, 2014 8:52 pm

New Interface: Generated Transactions Not Matching Mapping Upgrade

OK, but I haven't edited the source except to try to fix the problem.
I will try this evening.
Many thanks for your help.

Joseph Francis
Posts: 0
Joined: Thu Sep 04, 2014 8:52 pm

New Interface: Generated Transactions Not Matching Mapping Upgrade

I'm afraid it had almost no effect.

The mapping in the page I referenced above - "ChefEventArrive"

Image

The appery-generated "ChefEventArrive.js" source file has changed, whereas previously it read "Client" for the "eventCancelledBy" field, it now has a "\n" character (I can't even edit the mapping fields to insert it, Appery is really getting random data), and now I have a new junk field "eventChefHours".

Image

these are all reflected in the network activity when the transaction fires, with the junk fields being transmitted that are not in the mapping.

Image

Yurii Orishchuk
Posts: 0
Joined: Fri Feb 14, 2014 8:20 am

New Interface: Generated Transactions Not Matching Mapping Upgrade

Joseph,

I see you don't have "eventRating=0" parameter in your screen shot as you described above:

http://prntscr.com/59w6el/direct

Please describe what is not correct now.

Regards.

Maryna Brodina
Posts: 0
Joined: Thu Apr 05, 2012 7:27 am

New Interface: Generated Transactions Not Matching Mapping Upgrade

Hello Joseph!

Do you need any help yet?

Joseph Francis
Posts: 0
Joined: Thu Sep 04, 2014 8:52 pm

New Interface: Generated Transactions Not Matching Mapping Upgrade

Guys, I don't think you're reading my notes, or understanding the problem.

I AM NOT adding a parameter, in the above example "eventRating" but APPERY IS ADDING THE PARAMETER WITHOUT MY SETTING IT.

IF YOU READ THE "ChefArriveEvent.js" FILE, YOU CAN SEE THAT THE DEFAULTS ARE SET TO WRITE THE PARAMETER EVEN THOUGH I DON'T SET IT.

APPERY IS GENERATING FALSE MAPPINGS.

Here's ANOTHER EXAMPLE WHICH SPONTANEOUSLY HAPPENED YESTERDAY

page "ClientWaitChef"

mapping
Image

resulting .js file:

Image

I DO NOT SET IN THE MAPPING
"eventConfirmed": true,
I DO NOT SET IN THE MAPPING
"eventConfirmedPayment": "Authorized",
I DO NOT SET IN THE MAPPING
"eventCancelledBy": "Client",
I DO NOT SET IN THE MAPPING
"eventRating": "0",
I DO NOT SET IN THE MAPPING
"eventPurchased": false,
I DO NOT SET IN THE MAPPING
"eventOnway": false,
I DO NOT SET IN THE MAPPING
"eventArrived": false,
"eventCompleted": true,
I DO NOT SET IN THE MAPPING
"eventChefConfirmed": false,
I DO NOT SET IN THE MAPPING
"eventChefHours": "4",
I DO NOT SET IN THE MAPPING
"eventGift": true,

ALL OF THESE ARE TRANSMITTED FALSELY IN THE TRANSACTION AND IS PRODUCING GARBAGE IN MY DATABASE

THIS HAS BEEN GOING ON FOR OVER A MONTH WITH STILL NOT UNDERSTANDING THE PROBLEM.

Joseph Francis
Posts: 0
Joined: Thu Sep 04, 2014 8:52 pm

New Interface: Generated Transactions Not Matching Mapping Upgrade

Another Example:

page "EventConfirm"

mapping
Image

"EventConfirm.js" file produced
Image

the mapping is NULL, however the transaction in the javascript file is "TRUE", and the transaction sent to the database is "TRUE"

This came into the file in the last 24 hours of editing, without any action on my part.

I have to comb through every transaction to see if there are junk fields sent and set values to something which is reasonable.

The APPERY editor is producing junk in the .js files for "default" transaction values, not matching the mapping, nor the service defintion.

It is happening spontaneously, and without warning.

Joseph Francis
Posts: 0
Joined: Thu Sep 04, 2014 8:52 pm

New Interface: Generated Transactions Not Matching Mapping Upgrade

Another Example:

page "ChefEventDepart"

mapping
Image

resulting "ChefEventDepart.js" file
Image

the mapping is NULL, however the transaction in the javascript file is "TRUE", and the transaction sent to the database is "TRUE"

This came into the file in the last 24 hours of editing, without any action on my part.

I have to comb through every transaction to see if there are junk fields sent and set values to something which is reasonable.

There are transactions which don't have junk mappings. There is no pattern which ones do, and which ones don't.

The APPERY editor is producing junk in the .js files for "default" transaction values, not matching the mapping, nor the service defintion.

It is happening spontaneously, and without warning.

Yurii Orishchuk
Posts: 0
Joined: Fri Feb 14, 2014 8:20 am

New Interface: Generated Transactions Not Matching Mapping Upgrade

Hi Joseph,

I see problem in your app.

But when i restored your app from backup i can not see this problem.

See details:

1 In editor: http://prntscr.com/5cafzu/direct

2 In generated JS: http://prntscr.com/5cagu2/direct

Then i go ahead and try to set "false". And get this value in default request parameters.

After i set to "null" again and parameter has been removed defaults.

Also i see you use version of app that created before this thread started.

Did you try to create APP from backup as suggested above?

Regards.

Joseph Francis
Posts: 0
Joined: Thu Sep 04, 2014 8:52 pm

New Interface: Generated Transactions Not Matching Mapping Upgrade

I took the app, made a backup to a zip file, and then created it to a new, completely different app.

It changed behavior again, and added, in another transaction, a default value to a NULL field that didn't exist in the prior version.

I have a development, and production version. The process of moving the version from development to production seemed to create new bad default mappings.

In "ChefEventComplete", it added a new mapping for "eventGift" field to "TRUE", which I cannot remove using your technique.

I changed the field from NULL to FALSE, and then the mapping removed the TRUE result, and changed it to FALSE. When I set the parameter to NULL it removed the FALSE mapping and set the result to TRUE again, for no reason.

The editor is storing something which is not in the .js file and not in the mappings file, and it cannot be edited away. It is continuing to add mappings which I did not product, today is another example.

In my development version it worked fine, in the production version, created from a backup, it introduced the bug. When I ran the version that had tested perfectly in development, the production event created a new faulty transaction record that didn't exist in a completely separate development instance.

I'm really finding this instability amazing.

Return to “Issues”