Import Transactions not working

Thanks @kvvaradha, I suspected that, so I also installed it on my webserver which I can downgrade the PHP version.  I tried PHP 7.4 That had the same result.

thanks @kvvardha I'm finding all kinds of deprecations with 8.2.  I've fixed a bunch in my installations.  Should I post them on Github or Manits?  or Here?  How is the best way to communicate these kinds of code changes to the dev team?  Most of them are minor.   I just changed a bunch of variables in functions where the required variable has to go last in 8.2 ie:  function_name( $a, $b=5, $c) needs to be function_name ($a, $c, $b=5) type of thing.  I fixed a bunch of those.

Ok, here's an example:  /modules/import_transactions/includes/import_sales_order_entry.inc

PHP 8.2 produces deprecation warning  for line #11.  The constant must be moved to the end.  Moving $freightcost=0 to the end removes the warning:

function can_process($line, $customer_id, $branchNo, $reference, $date, $dimension_id, $dimension2_id, $delfrom, $deldate, $delto, $deladdress, $contactphone, $email, $custref, $shipvia, $comments, $exrate, $freightcost=0) {

There are other instances of this throughout this file.

It really would be quicker and easier to enter 5 transactions manually.

____________________________________________________

Have at least two installations of FA, use the extra for training yourself and then it doesn't matter if you make a mistake. Copy your backup from your existing actual to your training accounts; then use it before you use a new part of FA for your actual accounts. You'll learn more from your mistakes.

On your actual accounts backup at every opportunity and keep a comment/note of each backup.

____________________________________________________

Are you using $show_sql = 1; in config.php? it's close to the go_debug line; its very useful for debuging
____________________________________________________

Yes go to Setup>Fiscal years.

All transactions are historical

FA is worth it but does require effort, patience and resolve in the beginning. Keep going! You'll get there.

@pstevens
I have to admit its not easy to crack Import Transactions module. But once you link all fields correctly then its a piece of cake and you will be proud of yourself. From experience and maybe you have done this already you have to:

Reference should tally i.e If you want to import 004/2022 then your pattern should be {001}/{YYYY} and you make sure 004/2022 does not exist in the system. Also the system will not accept blank reference. It accepts a space (NULL). All fields in the spreadsheet should also be formatted accordingly..i.e Reference is General and Date is Date with the identical date format...etc..Also make sure the Fiscal Year that you are posting into is active and the Banking and GL Configuration has the Allow entry on non closed Fiscal years ticked.

Hope this will help.

@poncho1234
Yes the Allow Entry on non closed Fiscal Years is found in Access Setup under Banking and GL configuration.
I will take a look at apmuthu file and revert back here.

It didn't show any errors or warnings for me, were any showing for you?

I don't get any errors.  Even with one record, just nothing happens when I press the button.

I do however get an error in my sales orders (when I go and check after wards) 

processing_end(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "import_sales_cart" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide an autoloader to load the class definition in file: /share/MD0_DATA/Web/frontaccounting/sales/includes/sales_ui.inc at line 32

Ok I think I'm getting somewhere finally.  Aerodonkey thanks so much for the extra logging tip.  It's failing because it's not finding my customer ID.  So I assumed that the customer_id in the spreadsheet was the debtor number.  Is this correct?  Or is there some other customer ID.