Sugar logic to calculate days an opportunity has been open

We want to find out how many days an Opportunity in SugarCRM has been open, using a calculated custom integer field in SugarCRM Studio. I’m assuming you’ve already created a new custom integer field, likely called something similar to “Days open”.

The sugar logic to calculate the difference between two dates is this:

abs(subtract(daysUntil($date1),daysUntil($date2)))

and the sugar logic to do an if then else is:

ifElse(test,if_true,if_false)

The first test we’ll do is if the sales stage is “Closed Lost” or “Closed Won”, if it’s true, we’ll calculate the days between the create date and the expected close date. If the sales stage is something other than “Closed Lost” or “Closed Won” then we’ll calculate the days between the create date and today.

This makes our pseudo sugar logic formula look like this:

ifElse(
	or(
		equal($sales_stage,“Closed Lost”),
		equal($sales_stage,”Closed Won”)
	),
	calc_days_create_to_expected_close_date,
	calc_days_create_to_today
)

Which, when we update it with the real sugar logic parts becomes this:

ifElse(
	or(
		equal($sales_stage,"Closed Lost"),
		equal($sales_stage,"Closed Won")
	),
	abs(
		subtract(
			daysUntil($date_entered),
			daysUntil($date_closed)
		)
	),
	abs(
		subtract(
			daysUntil($date_entered),
			daysUntil(
				today()
			)
		)
	)
)

Now, removing all the spaces we get this:

ifElse(or(equal($sales_stage,"Closed Lost"),equal($sales_stage,"Closed Won")),abs(subtract(daysUntil($date_entered),daysUntil($date_closed))),abs(subtract(daysUntil($date_entered),daysUntil(today()))))

This post was written in response to a question on LinkedIn.

2013-11-04 Link Roundup

large__6921432697

photo credit: Rak Tia via photopin cc

2013-10-30 Open loops

large__8971665708

Off-topic, well, on topic, or both maybe: I’m finding it useful to write these ‘open loops’ as it’s just a bunch of links that I want to come back to, without losing them. Quite frankly it’s easier to find them here on my blog than anywhere else. I am the intended reader of these posts, but do let me know if your find them useful at all.

photo credit: MOLLYBLOCK via photopin cc

On writing

Steven Pressfield taught us the secret of real writers:

There’s a secret that real writers know that wanna be writers don’t, and the secret is this: It’s not the writing part that’s hard.  What’s hard is sitting down to write.  What keeps us from sitting down is resistance.

Makes sense.

Source: sourceofinsight.com

Importing Data Into SugarCRM

Working with SugarCRM (Pro, OnDemand) last week and discovered a wonderful thing!

SugarCRM has been designed to import record ID numbers from other systems. So long as the id numbers you’re importing are less than 36 characters, and are globally unique (not just unique to the entity, i.e. contacts, notes, accounts) you’re in business, you can simply import the legacy record ID into the Sugar ID field (see below on how to make it globally unique).

This is a great thing. Before knowing this, and with other systems, you need to create a custom field in each entity to store the legacy ID number, import the data into that entity, then export it with the new system’s ID number. You can then match up this new ID number with other data so that the relationships get maintained. This is discovery is for me a wonderful thing, others already know this as it was designed this way, but this will save me a lot of work.

One of the tips given to me by one of the SugarCRM support people was that if the ID isn’t globally unique, then simply suffix it (or prefix it) with something unique for that entity. For example, if Accounts and Contacts both have an ID of “ABCD-1234” you could suffix all the Accounts record ID’s with “_Acct” and the Contact record ID’s with “_Cont”. This effectively makes them globally unique. Do the same for any ID’s in other entities, for example, in the Notes table, any Contact ID’s would get suffixed the same way with “_Cont”.

Account Records Before:

  • ID, AccountName:
  • ABCD-1234, Doe Exports
  • ABCD-4321, Joes Toes

Contact Records Before:

  • ID, ContactName
  • ABCD-1234, Jane Doe
  • ABCD-4321, Joey Blowy

As you can see above, the ID’s are unique to the entity but not globally unique (and we do want them globally unique). By suffixing the ID’s we can make them globally unique as you see below:

Account Records After:

  • ID, AccountName
  • ABCD-1234_Acct, Doe Exports
  • ABCD-4321_Acct, Joes Toes

Contact Records After:

  • ID, ContactName
  • ABCD-1234_Cont, Jane Doe
  • ABCD-4321_Cont, Joey Blowy

This really does make it much easier import lots of data and keep the relationships between pieces of information. For example, Notes would then look like this:

Notes after:

  • ID, RelatedContact, RelatedAccount, Note
  • 123_Note, ABCD-1234_Cont, ABCD-1234_Acct, “Spoke with Jane re recent purchase.”
  • 456_Note, ABCD-4321_Cont, ABCD-4321_Acct, “Joey rang, wants to double his order.”

If only it were this easy importing into other CRM’s. Let me know if you have any questions about importing data into SugarCRM.

My Choices Led Me Here

I am here because of my choices, my decisions.
Because of my actions and my inactions.
Like it, or like it not.
That is the why.
You could accurately say “I chose to be here”.
The choices ahead, they will determine where I go.

Where are you?
And where are you going?
Are you choices leading you where you want to go?