Debugger erased.
fixes issue
21864: Discount Invoice Report is not filtering properly
Fixes issue
21885: Wrong action taken when payment is added to invoice.
Fixes issue
21907: When we modify the name of an element of the Account tree,
it changes the name of some the account combinations description.
Fixes issue
21901: Error in Asset Amortization calculation.
Fixes issue
21884: wrong calculation of ending date
for m_costing register under some cirumstancies.
[build time] 2.250 property is not read directly from file, but passed as param
[build time] Removed incorrect entries in model object and mapping tables
These entries were for generated windows which is not needed and caused a test
to fail.
related to issue
17491, related to issue
18343
Fixes bug
21931: Initial Client Setup and initial Organization Setup are failing
Fixed bug
21920 Fill accounting tab in tax rate for new taxes of Spain
Fixes issue
21669: Validation when exporting Database not working properly
There was a validation that was only being done to the tables that belonged to the module being validated, but not to the tables modified by that module. Now, if a module adds a column to a table that belongs to another module but forgets to add it to the application dictionary, the validation will detect the error, the same way it has been working for the columns defined in tables that belonged to the module being validated.
Fixes Issue
0021883: Linked items to the 'Table Reference' tab not working.
Fixed case where navigation through linked items fails where the table has primary and secondary keys.
Fixes issue
21910: When a widget is opened in a window it shows all its records
This issue was caused by the fix of the issue
16622. In that issue the ReadOnlyDataSourceServeld was changed so that it kept count of the number of records if the NOCOUNT parameter was set to 'false', as it was done with other datasources. In this case, in order not to break existing calls to the datasource, the count will only be prevented if the parameter is set to 'true', so if the parameter does not have any value (as it is in this scenario of the issue), the count will be done.
Fixes issue
21915. Fixes database consistency.
Related to issue
21905: Changed start date from 1-1-1950 to 1-1-1951
The start date has been changed from 1-1-1950 to 1-1-1951, so that if the user enters 1-1-50, it will be autocompleted to 1-1-2050, and if he enters 1-1-51, it will be autocompleted to 1-1-1951.
Fixes issue
21905: Range of dates available using the picker has been expanded
By default, the range of dates available using the picker was from 1-1-1995 to 31-12-2005. This range has been increased to 1-1-1950 - 31-12-2015.