Page 1 of 5

New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Fri Oct 10, 2014 4:16 pm
by Joseph Francis

I have a transaction to write a record to my database, updating only a few fields.

When I take a snapshot of the transaction on the network side, I update only the fields I requested in the transaction. After the upgrade, many fields are added to the transaction, with data I don't know where it comes from.

Before the upgrade, a "post" transaction snapshot of data sent:

Image

and the mappings

Image

notice that the fields EventCancelled and eventCancelledBy have no mapping data inbound.

After the upgrade, the identical transaction snapshot of data sent:

Image

notice that there are two fields added to the post command: eventCancelled: "true", and eventCancelledBy: "Client"

And the after-upgrade mappings:

Image

notice that the mapping is identical before/after upgrade, but after upgrade Appery is adding fields to the post command, apparently from some other mapping in my application to cancel a transaction.

Upon further checking, I found that several of the 'post' transactions are mixing fields from other transactions, not matching the mapping.

I have to roll back the upgrade a third time to continue development.

Thanks for your help here.


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Fri Oct 10, 2014 8:37 pm
by Kateryna Grynko

Hi Joseph,

Please check if there are such parameters in the service itself.


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Sun Oct 12, 2014 10:49 pm
by Joseph Francis

No, there aren't. You can also see from the screen shot, there are no defaults to the parameters.

The same parameters are passed in an entirely different screen and call. Somehow the conversion has added the parameters from another call to this one, and after further debugging, several other calls are mixed together.

To clarify: Nothing changed in the call, parameters or code. I literally did an upgrade, and captured the network call. Before the upgrade, you can see the results of the call, and after the upgrade, you can see that the parameters changed in what was passed to the network call, and they did not match the parameters as set up in the application call.

The upgrade is unusable for me if it randomly changes parameters in my database read/write calls.

What is your solution?


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Tue Oct 14, 2014 11:51 am
by Kateryna Grynko

Hi Joseph,

Please try unticking "Render all pages in one HTML file" in App Settings.


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Tue Oct 14, 2014 1:32 pm
by Joseph Francis

No problem. I will upgrade again and see if it's rendering like that, and report back.


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Mon Oct 27, 2014 8:44 pm
by Joseph Francis

Unfortunately, this has no effect. The interface I set up, and what is sent to the database are different in the upgrade, exactly the same as what I specified above.

What should I do. I cannot develop an application that fails in test with a random set of fields sent to the database.


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Tue Oct 28, 2014 4:01 pm
by Joseph Francis

Any update? I have given access to the application per prior request, and have no solution or messages.


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Tue Oct 28, 2014 9:36 pm
by Evgene Karachevtsev

Hello Joseph,

Could you please share your app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a, tell us its name and specify the service name and on what page it is situated?


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Wed Oct 29, 2014 1:34 pm
by Joseph Francis

Every single "update" service to my "event" collections has the problem.

Application is lekker, application is already shared with appery support.

I reviewed every "Update" database transaction to the events collection, and which fields I have mapped, and which fields are sent are almost randomly setup. Boolean values routinely are set to "true" whether or not I set the value, as are several numeric fields per the screenshot above. This affects a half-dozen screens in my application, and is very disruptive.


New Interface: Generated Transactions Not Matching Mapping Upgrade

Posted: Sun Nov 02, 2014 12:53 pm
by Joseph Francis

I've had to go through every update transaction in my application and adjust fields that are set by appery without the code setting values.

Something did not get set up correctly in the upgrade, this is the second set of services that were corrupted, along with the file upload service.