Remove Sequential Invoice Number in AddFunds

[kbwebsol]

Dear All,

Every where I Tried to find how remove Sequential Invoice Number when Add Funds because this major issue to maintain invoice number. So, I have created Hook for the same and Sharing to public access.

Just Upload file in  root_ directory/Include/hook.

In case need any customization this part let me know , Also found any error.

 

 

Remove_fund_Invoice.php

[brian!]

On 11/11/2019 at 11:14, kbwebsol said:

Just Upload file in  root_ directory/Include/hook. 

I think that you mean /includes/hooks 🙂

On 11/11/2019 at 11:14, kbwebsol said:

In case need any customization this part let me know , Also found any error. 

not so much errors, just a couple of suggestions for improvements...

this doesn't matter and so I only mention it for reference, but the = are optional in where statements, but required for joins.

personally, i'd use ->value instead of ->pluck in the line below as that would give you a single value as opposed to a list containing one item that pluck will.

$snv= Capsule::table('tblconfiguration')->where('setting', '=', 'SequentialInvoiceNumberValue')->pluck('value');

[kbwebsol]

49 minutes ago, brian! said:

I think that you mean /includes/hooks 🙂

not so much errors, just a couple of suggestions for improvements...

this doesn't matter and so I only mention it for reference, but the = are optional in where statements, but required for joins.

personally, i'd use ->value instead of ->pluck in the line below as that would give you a single value as opposed to a list containing one item that pluck will.

$snv= Capsule::table('tblconfiguration')->where('setting', '=', 'SequentialInvoiceNumberValue')->pluck('value');

Yes, I means /includes/hooks. 🙂

Thanks Brian for suggestion I will improve in feature.  

[brian!]

20 hours ago, kbwebsol said:

Thanks Brian for suggestion I will improve in feature.  

it occurred to me this morning, whilst contemplating the meaning of life(!), that your use of pluck is probably slightly better than using value as it's more backward compatible... untested, but I think your hook as written would also work in older versions when the use of pluck was defined slightly differently, whereas value would only work in releases from the last few years.

... and for something like this, were it's a long standing issue, so there's no knowing which version the user will have.