What is the Sugar alternative to SalesForce "Custom Object"

[tinkylou]

Hi,

My company uses SalesForce. I'm been cautious, but I have been impressed by how quickly we've been able to build additional functionality into the application through the use of custom objects, and how nicely it all ties together.

It struck us as we've been configuring, that really, if it weren't so darn expensive, we could build a whole bunch of company apps using the SF custom objects, alone. The only thing that frustrates me is that I can't do much validation.

However, as the mantra goes ... she's pricey, very pricey, so I'm looking around to see if Sugar will work for us. I've installed the open source solution, read around a little, and here's what I haven't figured out:

* What is the Sugar alternative to "custom objects"? Do I have to "hand-program" modules and install them? If I create an SF custom object via the SF interface, I can immediately link any other object as a lookup, etc, it's integrated with workflow and all other SF goodies. Can I do this with Sugar?

* The SF interface is extremely clean. It strikes me that, if one is going to move across from SF to Sugar, it may be MUCH easier if there is a "SF template" - one that looks very much like SF :-) ... Just to get the users over the initial bump. Has anyone designed something like this?

* In SF, if I search, and the search brings up no results for, say, leads - that section is omitted. In Sugar, it's not, and this clutters up the page.
* In SF, many sections of a page are collapsable, and it remembers what you collapse when you visit a similar page again. SImple idea, not that hard to implement, but it makes a huge difference in de-cluttering the page. Anything like this on the Sugar roadmap?

I'll put other ideas in a different post - to keep things uncluttered :-)

Thanks,
Tinky

[longreach]

1 - No - no custom objects - must code custom modules, for which there is a module loader

2 - While you're at it - no different detail views for different roles, no field level security, and no named/selectable or custom list views

3 - No SF-like template - can't say as I think that is much of a loss

4 - Sugar global search is basically terrible - use the module-level filter/searches which work well

5 - Collapsible sub-panels - yes, they are there - look harder I guess - Hide/Show link on right hand side

6 - This is 2 years since the SugarCRM company was founded - pretty darn good I reckon.

[tinkylou]

Hi Michael,

Thanks for the prompt reply! This is what I needed to know for my meeting this morning :-)

Not what I was hoping to hear, but I'm not despairing yet. Sugar now seems to me similar to the DNN portal project (just bigger, with a different function set). The module upload idea is quite similar.

1. Will there ever be custom objects? The "No Software" slogan bites at us programmers, but the business world just LOVES it. And configuring new functionality instead of coding it is a huge timesaver.
2. (and 4) That is a pity ... big pity. Any such plans (forgive me if there is a roadmap published somewhere, that I've missed).
3. ok

I guess, depending on the roadmap and how aggressive it is, I'll probably need to stick with SF for now. How fast does Sugar evolve (considering that SF, also, evolves continually)? Do you think in a year's time the picture may be different enough for people like me to be able to switch?

Thanks!
Tinky

[longreach]

I have not heard any talk of custom objects - so I don't think they can be expected any time soon.

Sugar does evolve quickly - used to be too quickly for business adoption in some ways - now a little slower and more manageable.

You are looking for some pretty high end features - I think you can expect to have to pay for those features, wherever you shop.

[niche]

* In SF, if I search, and the search brings up no results for, say, leads - that section is omitted. In Sugar, it's not, and this clutters up the page.

This a REALLY GOOD IDEA!
Sugar, please listen to this.
If there is no data to return from a search, then please don't show grouping header with no data below them, it forces you to have to scan really carefully. Of course it only takes a split second, but why show something that needn't be there?

[manoj]

Hi,

Custom object is not in Sugar Roadmap yet. But i will have a hard look at it. My understanding is : Module loader in SugarSuite provides a workaround to this and you really dont have to write code around a pre-defined object definition.

Sugar does evolve very rapidly and we listen to your feedbacks. Collapsible sticky detail views are under consideration and we are looking at ways to de-clutter the screens. Role based detail views are also under consideration.

So please keep all the feedbacks coming.

Thanks

[niche]

Sugar does evolve very rapidly and we listen to your feedbacks. Collapsible sticky detail views are under consideration and we are looking at ways to de-clutter the screens. Role based detail views are also under consideration.

Hi Manoj, thanks for the reply.
After immersing myself into Sugar and these forums over the last few weeks, one thing that keeps coming up from many different people in different circumstances is the inability (or difficulty) in updating/searching/filtering through the SEARCH and/or MASS UPDATE panels.
Clearly it wouldn't make sense to have every option and the kitchen sink in these panels or it would appear very cluttered and confusing, but giving the user some way to incrementally build a custom filter so that one could show:
ALL * LEADS * where * CITY * contains/equals * Los Angeles
or
ALL * OPPORTUNITIES * where * MYCUSTOMFIELD * equals * YES
or
ALL * LEADS * where * INDUSTRY TYPE equals * Architect

Does that make sense?