Carl Hicks

There should be, but let me tinker around a bit and see. This SEEMS similar in scope to retrieving email addresses for a given record, but I'm not sure. FYI......

What version of SugarCRM are you using?

Team Security is kinda silly, but it's a feature of Pro and Enterprise. If you want to make a record globally visible, just use: ``` a = SugarCRM::Account.new a.name =...

Also, if you want to view the current team assignments on a record in the web interface, you have to look for the "Teams" field in the "Other" subpanel. Teams...

Is something wrong with your instance? What release of Sugar are you running? (Click "About" in the web interface). Here's the behavior I get from a stock 6.2.2 Pro instance:...

Ooooooh, you're right. Turn on debugging to see what's going on! ``` SugarCRM.connection.debug = true ``` Basically `SugarCRM::Account.find(b.id)` calls `get_entry`, whereas `SugarCRM::Account.last` calls `get_entry_list`. It looks like `get_entry` doesn't return...

BTW, I've recreated this in 6.2.2 and 6.3.0 and logged a bug with Sugar as Bug# 48786. I'm going to mark this as a SugarCRM issue. Regarding your second bit,...

Oh, I see what you mean. So, the gem determines which fields are required by querying the server a la `get_module_fields` the first time a record is accessed/created. SugarCRM is...

I just cut a new gem that will allow you to bypass validation on save: ``` should "bypass validation when #save(:validate => false)" do u = SugarCRM::User.new u.last_name = "doe"...

That's an excellent idea. If you wanna take a crack at it, look at this commit: https://github.com/chicks/sugarcrm/commit/7047b61493d97dfbced1034ec1abac7b65a2b46a