Comments
The provided solution of "run once (in foreground)" is a bandaid and more of a workaround. What we need is to be able to start job queue entries without the user changing. Perhaps credential authorization can be stored internally when the customer user initially started the Entry. I realize this would take more invasive changes, but it's the only thing providing an acceptable user experience.
I know this isn't really the forum to provide help. Especially on a topic 5 years old. But you could also evaluate to store historical and/or binary data (the two biggest contributors to database size) outside of BC. Either in Azure Data Lake or Azure Blob Storage. Both also have a much more economical price setting.
There is also an urgend need to have an ER configuration EU Sales List (DE) that export an XML file, as for mass updates >1500 lines with ELMA its mandatory starting 1.12.25:BZSt - Zusammenfassende Meldung - Änderungen bei der Abgabe von Zusammenfassenden Meldungen mittels Massendatenschnittstelle ELMA ab dem 01.12.2025 - UpdateFor other countries it already exists, when will it be available for Germany?
We've had a few clients also comment about the same thing - the red asterisk on the PO is confusing for the user raising the PO. The above is a workable solution, or even if it was something on the Purchases & Payables Setup that would allow you to choose whether you want the field marked as mandatory/required.Most of our clients don't generate invoices from PO's, they only receipt the PO lines and then have solutions like Continia Document Capture to process their invoices, where they match to receipt lines.