PhpSpreadsheet | A pure PHP library for reading and writing spreadsheet files | Data Visualization library

I think there's no solution for this. So I just reduce the font size. When my data is small, the paper space will be wasted

Comments offer some good thoughts on basic options, summarized briefly:

1. Use a faster server
2. Make your algorithm for parsing your file (whatever it is) faster.

Either may alleviate your problem in the short term. However let's say your algorithm is well-optimized and your server is as fast as you're willing to pay for, both of which may be true for you and are often true in real-world cases. Let's also assume that your file size is somewhat unpredictable, so even when well-optimized and fast, you may need to support outlier cases of larger files that are slow to process.

It sounds like your workflow is (synchronously):

1. Client sends HTTP request to server with Excel file
2. PHP Server runs file parsing
3. Server returns an HTTP 200 (OK) and the parsed file when done. If a request takes > 600 seconds (or whatever the timeout is), it times out and returns a 504.

I would agree with the comments suggesting taking out Step 2 and putting it in background-job processing. This would make your workflow look like:

1. Client sends HTTP request to server with Excel file
2. Server sends the Excel file to a background job processor ASYNCHRONOUSLY, starting the processing but not waiting for it to finish.
3. Server returns an HTTP "201 Created" saying the server has started processing the file.
4. Client polls a Job Status endpoint on the server every n seconds to check if the job is done

There are a LOT of different ways to do this (the above background processing link details a few Azure-esque ways).

One Azure-centric way I can think of is to use a function app triggered by a queue. In this case, your server could accept an Excel File, persist it somewhere (or your client could upload it directly to Azure Blob Storage), and then adds an entry to your Queue, saying where your file to be processed is. Using a queue trigger, this can then automatically trigger your function app code, which can pull the oldest message from your queue, go and find the file to be processed, process it in as much time as it takes, and then upload the "processed" file back to blob storage for client consumption.

I know less about PHP background job tooling, hence the Azure-ness of the above suggestions, but there are definitely dozens of other ways to do the same basic workflow proposed above, and the benefit of the above is that you can implement it using basically any language you want, the core architecture remains the same.

phpoffice/phpspreadsheet v1.19.0 requires php: ^7.3 || ^8.0

1. Check your installed PHP version by running this command php -v. Make sure it's greater or equal to 7.3.

2. Secondly, make sure that the PHP version declaration in the composer.json file is also greater or equal to 7.3. I.e:

Apparently DateTime::createFromFormat() adds the current time if you don't specify it.

The solution is to add ! in the format to reset all the fields to zero-like values which I got from this comment.

You are overwriting the array in the inner loop on the second pass

The problem occurs because you are generating the filename twice, and it's time-dependent, so it can be different each time. Define it once in a variable and then use it for both things:

The params of Rule::requiredIf should be a callback function that you need to custom the rule and input.

It's better to change Rule::requiredIf('*.0' === 'PRODUCTION-PROJECT') to 'required_if:*.0,PRODUCTION-PROJECT"'

so the correct code is :

Here's a working sample code:

Counting rows will bring you problems whenever you remove a single record from the table: You won't be able to insert new rows if your primary employee_id field has UNIQUE key, or you will start inserting duplicated IDs.

Generating the ID in PHP isn't my recomendation either since you could face integrity problems if two records are trying to be stored simultaneously.

I would use the default model's model_id field with autoincrement to make sure that I won't have problems with id assignation, and inmediatly after saving the record I would update the id for the employee_id field which can be also keyed as "primary" in order to be indexed and accessed efficiently.

For example: