Importing Backup JSON #9262
Replies: 3 comments 1 reply
-
This particular error is not about the key not existing as such, but the index to the imported payment ID not existing. Do you see payment records in your database? My guess is that the payments are importing, however the paymentables are not. Is there anything different from standard in regards to the data? or is it importing a file that was exported cleanly from the app? |
Beta Was this translation helpful? Give feedback.
-
@turbo124 thanks for the reply! Both payment records, and payment tables are blank I've been doing some digging, and it looks to be related to missing data in paymenttable. I am importing a backup.json file from the app. However, I dirty deleted some client data via the API, which seems to have broken some overall referential integrity. Is there an easy way to wipe and re-import, ensuring I don't keep getting an import fail |
Beta Was this translation helpful? Give feedback.
-
@shaneoreilly your best bet here is to export as CSV and import that way. The data will be much cleaner. |
Beta Was this translation helpful? Give feedback.
-
Setup
Interface
Checklist
Describe the bug
When I try to import a JSON backup, the laravel.log file says the following:
[2024-02-05 16:22:18] production.INFO: Resource payments not available.
There is no other logs after this.
I also get a failure notification stating:
There was an error importing the company data, the error message was:
The Import failed due to missing data in the import file. Resource payments not available.
The Invoicing module is enabled, and the backup JSON contains ~4,000 lines of Payment data:
Any ideas what could be causing the issue?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions