Error Try Commit in CommitRecordAction

[Q&A] General
1

A while ago after a components update I get this message in my application Error calling TryCommit in CommitRecordAction: Invalid column name 'default_delivery_to_country. How can I solve this? The indicated field is expected in “sales_price_list” table. Thanks in advance.

I have investigated this further in Expression Debugger: The datamodel says that the field is present in table “salespricelists”. When I evaluate it I get the indicated error. That the field is not known in sql. Should the field be added or should it be removed? And how can I do that?

image
image1205×253 20.6 KB

image
image852×340 22.6 KB

2

Hi Reza,

Did you try to open the model in the architect? to check if maybe the name of the field contains hidden spaces or something like this?

3

Hi Reza, when you get this error, it typically happens when your database has not been updated.

If this is the case, you usually have a warning in your login-screen, about here:

image
image460×218 2.15 KB

You could also check if the database version matches the application version.

the revision of the codebase is here:

image
image304×106 1.8 KB

Whereas you can find the database revision in the Expression debugger using:

{versioninfo, revision}

image
image833×181 7.31 KB

As you can see, in my application they are the same.

This error is rare but can happen in two cases:

  1. When you use the database copy tool, and copy the database from a different revision. For example, when you copy the Production database in revision 10 to Acceptance on revision 11, this occurs
  2. When you installation failed on the update script, but you still manage to log in.

In case (1), you should manually run updatedb. This goes as follows:

  1. Go to Deployment
  2. Send a maintenance package to your application
  3. Go to the installer
  4. Start the maintenance flow “developer mode”
  5. Access your application using: default.aspx?updatedb=yes
  6. Finish the maintenance package

In case of (2), find out why the update script failed. Abort and revert the installation, fix the update script and deploy again.