Migration fails - MG

@Vasili Kapylou , thank you!

Closing as done.

Hi @Magda Zacharska @Denis!

After the migration of mod-data-export-4.4.2 to 4.5.0 version we faced the problem with migrations scripts that was not performed any needed changes in the mod-data-export schema, but with rapid and excellent help from Viachaslau Khandramai and guys from Firebird team we quickly fix this issue by releasing new patch version of the module (mod-data-export-4.5.1). 
After updating module mod-data-export-4.5.0 to 4.5.1 version the migration scripts are fully executed and performed all expected changes.

For example, one of the changes that we can see in the DB schema is the new field "default":

{
  "id": "*****",
  "name": "*****",
  "default": false,
  "metadata": {
    "createdDate": "2020-11-19T04:30:06.727",
    "updatedDate": "2020-11-19T04:30:06.727+00:00",
    "createdByUserId": "*****",
    "updatedByUserId": "*****"
  },
  "userInfo": {
    "lastName": "*****",
    "userName": "*****",
    "firstName": "*****"
  },
  "mappingProfileId": "*****"
}

Additional OKAPI log:
{
"id":"mod-data-export-4.5.1",
"from":"mod-data-export-4.5.0",
"action":"enable",
"stage":"done"
}
 

Hi @Magda Zacharska , @Denis , I assume we can close it as done because MG env was successfully updated with new release version this was the initial request.

@Vasili Kapylou can confirm that module was successfully migrated and migration scripts passed without issues.

Thanks,

Slava

Hi @Viachaslau Khandramai - how do we know that the fix resolved the problem?