Call Outcome set to "Array"

[Deland01]

Here's a good one for all you SQL programmers.

I colleague of mine said someone scheduled a call yesterday from a lead. Then closed the call as Outbound & Held. The call wasn’t attached to the Lead, in fact it wasn’t in sugar at all. So she scheduled another call in the exact same way & this seamed to work fine. The new call showed up under the history ok but no sign of the old one.

Now I wasn’t there to witness the first scheduled call, or the second one she made so I don’t know if she's done something wrong along the line.

However I checked the SQL tables through phmyadmin for all calls attached to the Lead in question & found x2. The call made today had the status of Held but the other call she made yesterday had the status of Array. When I changed Array to Held the call showed up in sugar on the bottom of the Lead??

So my questions are:

1. Does anyone know why the call was set to the status of Array

2. What is Array?



P.S. the only options I have on the Status box are the sugar standard of Planned, Held & Not Held.



.

[hkphooey]

I've seen this in a couple of other places. My best guess is that the database is trying to stuff an array into a field that won't accept it. EG if you have the results of a Multiple Select field and you try to put them into a text field in a database.

Would that make any kind of sense in your context?

[Deland01]

Erm, kinda yeh. I understand what an array is in terms of when you would use it in programming. To declare a set of variables but the bit I dont get is why sugar is trying to add Array when it should only be allowed to insert Held or Not Held?

[Deland01]

Ok this is quite worying now, same query again about people scheduling calls that arent in sugar........


I checked the calls SQL table & found 49 different calls with Array in the status field.

Does anyone know what php file controlls the command to write the data when you close a call? I'm looking at the call status field.

[hkphooey]

I'm in the dark here a little as well, but lets try to clarify what I was saying earlier.

The times I've seen this before, its been due to adding a custom field (or sometimes a standard field) to a page using the Studio. What happens is it adds the field as the wrong type so a normal drop down is added as a multiple select. If this happens in an edit layout, when you Save the page, then it tries to stuff a multiple select into a text field, and what actually goes in is the word Array. This is how I understand it. And I have no idea why the field is put in the form as a multi select.

You can try removing the field from the page in question and then re-adding it. Maybe that will work.

If not, then you may have to get down and dirty by editing the file manually. These lie in the modules directory I think. Look for the field and see if it is a multiple select. If it is, try to copy the code from a drop-down that you know is OK. Lots of hacking, so take lots of backups, natch.

And of course I could be completely wrong.

[Deland01]

It seams to have calmed down now and only saving as 'Planned', 'held' or 'not held' as it should do. Its quite strange as I've made quite a few customisations to sugar but the only thing I haven't touched is the status field.

I'll keep my eye on it and if it gives me any more bother I'll remove & re-add it.

Thanks very much for the detailed answer, it all makes sense now. I did take a look in the .php files and the status field does say enum and looks to be ok so I'll just have to wait and see.

[agupta]

This issues was addressed in 450j. If you do not want to take the complete patch, then just look at include/formbase.php from the package.

-Ajay

[Deland01]

An even better answer. thank you