Changes and issues relating to custom plugin for client

[DannyC]

Hi,

This is regarding the custom sales order plugin developed for one of Attkey's clients & deployed recently. See the Jiwa case 0000018978.

One other change required is the custom field Despatch (Despatch Method).

I had developed a plugin which populates the contents based on a custom table.
It was developed based on this forum post http://forums.jiwa.com.au/viewtopic.php?f=26&t=205

Attached to the case is the table structure, the contents, and my plugin which already had several of the custom fields which are also in the new client plugin. Those attachments can be found on case 0000018978.

In addition to making the Despatch look up the data from the table, could you also check all the values of the other combo box fields – for example PayStatus is slightly different. I haven’t had time to check every custom field and the values.

Another issue relates to other plugins attached to that case.

I have some debtor custom fields. I have attached the plugin which implements them.

The plugin Check Pay Status of Debtor reads some debtor custom fields and sets the value of the PayStatus field on sales orders.

When creating a new sales order I am getting an error “Input string was not in a correct format. Module: ParseDouble”. It has something to do with the plugin Check Pay Status of Debtor as when I disable it the error no longer appears, however it is essential for their day to day functions that the plugin is working.

I have also attached a slightly tweaked version of the <Client> Custom Sales Order screen to better match the values they expect in some of the custom fields.

Thanks

Danny

[Mike.Sheen]

When creating a new sales order I am getting an error “Input string was not in a correct format. Module: ParseDouble”. It has something to do with the plugin Check Pay Status of Debtor as when I disable it the error no longer appears, however it is essential for their day to day functions that the plugin is working.

Hi Danny,

This error means that something is trying to put a value which isn't a number into a number. If you have custom fields, then you may have some bad data there.

As for the case related matters of your post - if you've got cases in the case system for these issues, then they will be dealt with - no need to post here about them - we look at cases in the case system also.

Mike

[DannyC]

if you've got cases in the case system for these issues, then they will be dealt with - no need to post here about them

OK. Beth told me you only look at cases a couple of times a week, whereas the forums are checked all the time. Anything to do with plugins should be asked on the forums.

Anyway, I had assumed it was something to do with incorrect datatypes, but I have scoured the code and can't see where the input isn't a number. Will look again but I think I may need a real coders eye.

Cheers

[Scott.Pearce]

it was something to do with incorrect datatypes, but I have scoured the code

You should check the values coming in from the custom field value table. Your code may be expecting a numeric, but getting something non-numeric (like an "a"). This is possible because custom field values are stored as varchars in the database. You could add some defensive code (ie. call isNumeric) when reading in the custom data.

[Mike.Sheen]

Beth told me you only look at cases a couple of times a week, whereas the forums are checked all the time.

That is true, but we only respond to forum questions between milestones in our daily work, and if the forum post is something that is going to take more than just a few minutes, we will defer responding until we have enough time to respond with what we think is an adequate response. As forum posts are often right within our knowledge domain (which is programming - nobody seems to use the forums for anything else for some reason) we can often respond in a timely fashion. Cases we get assigned, on the other hand are usually customisation requests, or customer specific issues with the software - which usually take a fair chunk of time - so we dedicate a day or two a week to work through the case queue which has been assigned to the programming department.

Mike

[DannyC]

OK, understood. I suspected similar anyway but when 'm directed to post questions on the forum, I do it!

Anyway, I think I have sorted out the

Input string was not in a correct format. Module: ParseDouble

error.

I just need the new sales order plugin to read the Despatch custom table to populate the combobox.
As a temporary workaround I can modify the plugin will all current values required but as the Despatch custom table is editable by the client the contents can change from time to time.

Cheers