I just wanted to check in regarding some inconveniences I have been experiencing with Zoho CRM.

1) Disappearing Function Namespace

• Problem: When writing a custom function through related list (any module) if you edit the params area and do not specify either: custombutton or workflowspace for a namespace - upon saving you will NOT be able to later retrieve and update the function.

• Side Effects: Assuming you wrote a free function you can still CALL the function and get your returned value via the global namespace. You can also still see the custom function from anywhere in deluge / creator scripting when going to Call Function -> Application: mycustomfunctions -> Namespace:default namespace. 

• Problem: If you create a custom function for a related list (again any module) and the save fails because of syntax / error (missing semicolon, bracket, etc..) it will notify you of the failure. Upon fixing any errors if you try to resave using the save button it does nothing.

• Side Effect: Function and corresponding code are lost and you must start over from scratch. (better to copy it all to clipboard before trying to save because u only got one shot!)

• Problem: Due to criteria limits you are forced to try to grab bulk data and iterate over your objects. (increasing the work load on the servers overall i assume). I have experienced an error many times due to exceeding the work flow limit. My problem in particular could be solved by simply using a >= && <= operator. Saving me headache and server workload overall. I understand it might be hard to implement multiple field search criteria but a numeric value greater than less than for the same fields seems reasonable. 

• Use Case: Maybe you have customers age as a field. You want to target a certain range. record.get("age") >= 18 && record.get("age") <= 30. Instead the current option would make u grab all above 18 (maybe u have users that are much older, yielding a lot of unnecessary results). Again, totally get not wanting to implement complex criteria but this seems pretty reasonable and would seem to benefit both Zoho from a hardware standpoint and and us as users from a productivity standpoint. 

• In zoho zrm you are not able to use try catch blocks to prevent undefined behaviour / errors. I initially thought this was a limitation of the creator api but come to find out during my creator.zoho trial that it is in deed available to creator users. Is this really something that warrants a premium? I kind of consider it almost cruel to now that i know it is implemented and working on zoho platforms, just not CRM. This is far from a luxury item in anyone's mind i'm sure. Please consider enabling it in zoho CRM as well.