Evaluating Blesta for use in an environment which has some amount of Existing System that we would have to integrate with. The one that looks hard to me is, for every invoice, we need to generate an invoice number in another system, and we need to display the corresponding invoice number on our invoices. I've found a couple of threads on the Blesta forums about modifying invoice templates to add things like custom fields from clients, but that's per-client data. I need a per-invoice datum. (Actually probably more than one, because historical reasons are historical.)
Looking at the actual code for the invoice model, I did not see any hooks for per-invoice custom fields. It's probably within my ability to add such a thing, but before I start committing to any large projects, did I miss an obvious thing?
Question
seebs
Evaluating Blesta for use in an environment which has some amount of Existing System that we would have to integrate with. The one that looks hard to me is, for every invoice, we need to generate an invoice number in another system, and we need to display the corresponding invoice number on our invoices. I've found a couple of threads on the Blesta forums about modifying invoice templates to add things like custom fields from clients, but that's per-client data. I need a per-invoice datum. (Actually probably more than one, because historical reasons are historical.)
Looking at the actual code for the invoice model, I did not see any hooks for per-invoice custom fields. It's probably within my ability to add such a thing, but before I start committing to any large projects, did I miss an obvious thing?
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.