Reports updated mostly for currency conversion, split where appropriate and ignore Duplicate Tx #60
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed so account name come from SQL and no editing of htt is needed.
Using SQL values from currency table to format correctly currency values on the reports using javascript.
The report has two parameters in SQL, one to set to Calendar or Financial Year and the 2nd to set the years the report should show collated values for.
…eral-reports into SQL-Changes-1.3.3-v7
Display the currency the report is in (using the account's currency setting) and format the amounts as numbers correctly with the dec & group characters.
Pickup the latets currency conversion from the CURRENCYHISTORY_V1 table. If there are no value, then use CURRENCYFORMATS_V1.BASECONVRATE.
Display values in the account's currency formats.
Pickup the latets currency conversion from the CURRENCYHISTORY_V1 table. If there are no value, then use CURRENCYFORMATS_V1.BASECONVRATE.
Now get the conversion rate from CURRENCYHISTORY_V1, if not found then uses CURRENCYHISTORY_V1.BASECONVRATE
Pickup the latets currency conversion from the CURRENCYHISTORY_V1 table. If there are no value, then use CURRENCYFORMATS_V1.BASECONVRATE. Changed the SUBCATEGORY_V1 to left join as not all Categories have a subcategory (Other Expenses) and Transactions can be put at Category level by user.
Format currency and deal with various currencies.
- Switch to ChartNew.js - Exclude Void & Duplicates & Transfers - Switch to base currency using History values or default - Display currency
- SQL now pulls both the Currency rate from currency record and latets historical currency rate - Displayed prefix & suffix symbol(s) of the currency
Displayed example formatting for each currency.
-- Convert to Base Currency from Tx Acc Currency using Curr History or Curr Conv 2 Base Rate -- CheckingAccount also now use SplitTransactions (check CATEGID = -1)-- Billdeposits Account also now use BudgetSplitTransactions (check CATEGID = -1)
…eral-reports into SQL-Changes-1.3.3-v7
Support for accounts in multiple currencies converted to base currency. Conversion uses latest History Rate, or Currency Record rate. Correction to Total column, now include current month's expenses.
…eral-reports into SQL-Changes-1.3.3-v7
- support accounts in difference currencies - display curency of account on report - pickup currency conversion rate from History if available - report now picks up Credit Limit from the account record.
- correct date range - Remove zero dataset - more description
- Displays the amounts in currency of the account - HTML5 check on template - refined SQL to reduce number of JOINS
Save the template in UTF8 for the internation characters
Upgraded to use the ChartNew.js script file.
Used Historic Values before using Conversion Based currency rate
Used Historic Values before using Conversion Based currency rate Report gets Payee from SQL.
New report showing same as built-in but for multiple years.
Remove the legend js and use the options for legend.
- Correct graph value titles (from color) - add legend to graph - format description.txt
Fixes and tidy the report.
- display account values in account currency - display totals in base currency - use historical currency value before currency base conv value
Check_gm.py - now includes traceback for more informative error reporting - opens files in read text mode (binary was failing) and force encoding utf-8 tables_v1.sql - copy the file from v7 release as CURRENCYHISTORY_V1 table (and other DB changes) are not in the file in master repository
commented out v3 line as travis-ci is upgrading soon
Reference in SQL changed case, Lua needs to change also as it's case sensitive
On Apr 167th, travis-ci.org moved to Python 3, print syntax updated
Missing the ="" in the where clause. Fixed.
|
Please remove |
|
@siowena please re-add |
|
Will do on the .gitignore file. However, the SQL check_gm.py now fails travis-ci after the DB V12 checks due to tablename changes - is that OK, or am I missing something? |
Shouldn't have pushed from mac
|
We have reports for the old db schema only - so it's ok SQL queries are not working with MMEX 1.4.x db. We need something like #52 to support users with different MMEX versions. |
- Report was present twice with spaces and underscores in the name - Renamed report name to bring in line with other report namings and removed the duplicate report
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using some of the points in #53 as a guide (and also updated as I needed them to work)
AccountForecast
AccountSummary
AccountTrend4
AttachmentList
BlankNotes
BudgetMonitoringCurrenctMonth
BudgetMonitoringLastMonth
CategoriesStatLast12Months
CategoryForecast
CategoryTrend
CreditReport
CreditReport2
CurrencySummary
DepositVsExpensesAndLoadRepaymentsByMonth
ExpenditureHistory
IncomeVsExpenseTransactionsByYear
PayeeTrend
SavingsProgress
usercoloredtransactions
YearlyExpenseAndRevenue